Systems and methods for performing sidelink communication in time-sensitive networks

Abstract

At least one aspect of this disclosure relates to a wireless communication method. The wireless communication method may include: a first wireless communication device sending a message to a second wireless communication device, the message including timing configuration auxiliary information for sidelink communication. The wireless communication method may also include: the first wireless communication device receiving timing configuration information from a network.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for sidelink communications in time-sensitive networks. Background Technology

[0002] The standards organization 3GPP is currently in the process of specifying a new radio interface called 5G New Radio (5G NR) and the next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and the User Equipment (UE). To facilitate the implementation of different data services and needs, some elements of the 5GC (also known as network functions) have been simplified based on software or hardware, allowing them to be adapted as needed. For industrial solutions, sidelinks can increase reliability by providing additional transmission paths. Device-to-network connections (NR-Uu) and sidelink connections (NR-PC5) can coexist. This increases redundancy; for example, in motion control use cases, a failure of one communication path can be compensated for by switching to another. However, this is not yet standardized in 3GPP and requires solutions involving dual-modem devices above the radio layer. In existing technologies, sidelink communication cannot support time-sensitive communications (TSC) and time-sensitive networking (TSN), and different UEs cannot synchronize with each other. Therefore, sidelink cannot support deterministic communication. Summary of the Invention

[0003] The exemplary embodiments disclosed herein relate to solving problems associated with one or more problems presented in the prior art and provide additional features that will readily become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of illustration rather than limitation, and it will be apparent to those skilled in the art who read this disclosure that various modifications can be made to the disclosed embodiments that still fall within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication method may include: a first wireless communication device sending a message to a second wireless communication device, the message including timing configuration assistance information for sidelink communication. The wireless communication method may also include: the first wireless communication device receiving timing configuration information from a network (e.g., network 100). The timing configuration assistance information associated with a first clock of the first wireless communication device may include at least one of the following: priority of the first clock, class of the first clock, accuracy of the first clock, stability of the first clock, Global Navigation Satellite System (GNSS) indication, Time-Sensitive Networking (TSN) indication, status of the Precision Time Protocol (PTP) port of the first wireless communication device, or multicast header indication.

[0005] The timing configuration information may include at least one of the following: whether the first wireless communication device can act as a source clock and send timing-related information to one or more other wireless communication devices, the priority of the first clock of the first wireless communication device, the identifier of the first clock, or the type of the first clock. The wireless communication method may include: the first wireless communication device receiving timing configuration information, timing configuration auxiliary information, or a first capability message from a second wireless communication device. The first capability message includes whether the second wireless communication device supports sending or receiving timing information. The wireless communication method may include: the first wireless communication device sending timing configuration information, timing configuration auxiliary information, or a second capability message to the second wireless communication device. The second capability message includes whether the first wireless communication device supports sending or receiving timing information. The wireless communication method may include: the first wireless communication device sending either the received timing configuration information or timing configuration auxiliary information to the network.

[0006] The wireless communication method may include: in response to satisfying at least one of the following conditions, a first wireless communication device determines a source clock and transmits timing-related information to one or more other wireless communication devices. These conditions include: the first wireless communication device supports sending timing configuration information and the second wireless communication device supports receiving timing configuration information; the first wireless communication device is a head user equipment (UE); the priority of the first clock is higher than the priority of the second clock associated with the second communication device; the class of the first clock is higher than the class of the second clock; the accuracy of the first clock is higher than the accuracy of the second clock; the stability of the first clock is higher than the stability of the second clock; the first wireless communication device is directly synchronized to GNSS; the first wireless communication device is directly synchronized to a network node; the first wireless communication device is connected to the TSN controller or TSN GM clock via a wired or wireless connection; the first clock is the TSN timing GM; the PTP port is configured in Leader or Master state for sidelink communication between the first and second wireless communication devices; the PTP port is configured in Leader or Master state for source / target ID associated with sidelink communication between the first and second wireless communication devices; the synchronization source priority of the first wireless communication device is higher than the synchronization source priority of the second wireless communication device; the synchronization source of the first wireless communication device is different from the synchronization source of the second wireless communication device; the type of the synchronization source of the first wireless communication device is different from the type of the synchronization source of the second wireless communication device; or the identifier of the synchronization source of the first wireless communication device is different from the identifier of the synchronization source of the second wireless communication device.

[0007] The wireless communication method may include: the access layer (AS) of a first wireless communication device obtaining at least one of the following information from its non-access layer (NAS): multicast indication, TSN indication, the status of the PTP port of the first wireless communication device, or the wireless communication device being a synchronization source. The wireless communication method may also include: in response to at least one of the following conditions, the first wireless communication device determines to send timing configuration information to the second wireless communication device: the first wireless communication device is a head UE, the first wireless communication device is a synchronization source, the first wireless communication device is connected to a TSN controller or TSN GM clock via a wired or wireless connection, the first clock is a TSN timing GM, or the PTP port is configured in a Leader or Master state for target ID D2.

[0008] The wireless communication method may include a first wireless communication device transmitting wireless interface-related information including either a referenceSFN or a referenceTimeInfo. The wireless interface-related information is used to determine a timestamp. The wireless interface-related information is carried by a sidelink RRC message. The first wireless communication device periodically transmits the wireless interface-related information. In response to recognizing a change in any of the wireless interface-related information, the first wireless communication device transmits timing configuration information.

[0009] The wireless communication method may include: a first wireless communication device determining itself as a source clock and transmitting timing-related information to one or more other wireless communication devices. Before determining itself as a source clock, the first wireless communication device receives a message from a second wireless communication device, the message including timing configuration assistance information, timing configuration information, or a first capability message. The first capability message includes whether the second wireless communication device supports transmitting or receiving timing-related information.

[0010] The wireless communication method may include, in response to at least one of the following conditions, a first wireless communication device determining itself as a source clock and transmitting timing-related information to one or more other wireless communication devices: the first wireless communication device supports transmitting timing configuration information and the second wireless communication device supports receiving timing configuration information; the first wireless communication device is a head user equipment (UE); the first clock has a higher priority than a second clock associated with the second communication device; the first clock has a higher class than the second clock; the first clock has higher accuracy than the second clock; the first clock has higher stability than the second clock; the first wireless communication device is directly synchronized to GNSS; the first wireless communication device is directly synchronized to a network node; and the first wireless communication device is connected to a TSN controller or TSN via a wired or wireless connection. The GM clock connection is used, with the first clock being the TSN timing GM. The PTP port is configured in Leader or Master state for sidelink communication between the first and second wireless communication devices. The PTP port is also configured in Leader or Master state for the source / target ID associated with the sidelink communication between the first and second wireless communication devices. The synchronization source of the first wireless communication device has a higher priority than the synchronization source of the second wireless communication device. The synchronization source of the first wireless communication device is different from the synchronization source of the second wireless communication device. The type of the synchronization source of the first wireless communication device is different from the type of the synchronization source of the second wireless communication device, or the identifier of the synchronization source of the first wireless communication device is different from the identifier of the synchronization source of the second wireless communication device.

[0011] The wireless communication method may include, in response to at least one of the following conditions, a first wireless communication device determining itself as a source clock and sending timing-related information to one or more other wireless communication devices: the first wireless communication device is a head UE; the first wireless communication device is a synchronization source; the first wireless communication device is connected to a TSN controller or TSN GM clock via wired or wireless communication; the clock of the first wireless communication device is connected to the TSN timing GM; or the PTP port of the first wireless communication device is configured in a Leader or Master state for use with target ID D2. The wireless communication method may include the first wireless communication device sending wireless interface-related information including referenceSFN or referenceTimeInfo. The wireless interface-related information is used to determine a timestamp. Attached Figure Description

[0012] The following description details various exemplary embodiments of this solution with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the solution to aid the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0013] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein may be implemented; Figure 2 Block diagrams of example base station and user equipment apparatuses according to some embodiments of the present disclosure are shown; Figure 3 An example method is shown according to an embodiment of the present disclosure for a user equipment (UE) to maintain synchronization radio interface timing over a network in a unicast situation; Figure 4 An example method is shown according to an embodiment of the present disclosure for a UE to maintain synchronization radio interface timing in the absence of a network in a unicast scenario; Figure 5 An example method is shown according to an embodiment of the present disclosure for a UE to maintain synchronization radio interface timing with network assistance in a unicast scenario; Figure 6 This illustrates an example method for a UE to maintain synchronization radio interface timing via a network in a multicast situation, according to an embodiment of this disclosure. Figure 7 An example method for AS layer maintenance synchronization radio interface timing for a UE according to an embodiment of the present disclosure is shown; Figure 8 An example method for maintaining synchronization radio interface timing for a NAS layer of a UE according to an embodiment of the present disclosure is shown. Figure 9 A flowchart illustrating sidelink communication for a time-sensitive network according to an embodiment of the present disclosure is shown. Detailed Implementation

[0014] Mobile communication technology and environment Figure 1 An example cellular communication network and / or system 100 according to embodiments of the present disclosure is illustrated, in which the techniques disclosed herein may be implemented. In the following discussion, wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as “network 100”. Such an example network 100 includes base station 102 (hereinafter referred to as “BS 102”; also referred to as a wireless communication node) and user equipment device 104 (hereinafter referred to as “UE 104”; also referred to as a wireless communication device) capable of communicating with each other via communication link 110 (e.g., a wireless communication channel), and a set of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating within its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0015] For example, BS 102 can operate within its allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" that can practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0016] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, as described above, system 200 can be used in applications such as... Figure 1 The wireless communication environment 100 is a wireless communication environment in which communication (e.g., transmission and reception) data symbols are used.

[0017] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment device 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other via a data communication bus 220 when necessary. UE 204 includes a UE (User Equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other via a data communication bus 240 when necessary. As described herein, BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission.

[0018] Those skilled in the art will understand that system 200 may further include, in addition to Figure 2 Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are typically described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software can depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art, when learning the concepts described herein, can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0019] According to some embodiments, UE transceiver 230, which may be referred to herein as "uplink" transceiver 230, includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210, which may be referred to herein as "downlink" transceiver 210, includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 can be coordinated in time such that uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250 while downlink transmitter is coupled to downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250 simultaneously with the uplink transmitter being coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0020] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 that are appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to specific standards and associated protocols in application. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0021] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented in various types of user devices, such as mobile phones, smartphones, personal digital assistants (PDAs), tablet computers, laptop computers, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0022] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from memory modules 216 and 234 and write information to memory modules 156 and 166 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may also include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0023] Network communication module 218 typically represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 102. For example, network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling base station transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a specified operation or function, the terms “configured for,” “configured to,” and variations thereof refer to means a means, component, circuit, structure, machine, signal, etc., physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0024] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") defines the conceptual and logical layout of network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven sub-components or layers, each representing a set of concepts providing services to the layers above and below it. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Media Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer may be another layer.

[0025] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use this solution. It will be apparent to those skilled in the art that various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and shown herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0026] Systems and methods for performing sidelink communication in time-sensitive networks For Time-Sensitive Network (TSN) type service communication, an important aspect is that the communicating UEs should be synchronized with each other. According to existing technology, UE 104 can obtain time information from the network side. However, there is no solution to keep different UEs 104 synchronized with each other. For example, suppose UE-1 and UE-2 establish a PC5 connection and perform sidelink communication to transmit TSN type services, and UE-1 obtains time information from network node 1, while UE-2 obtains time information from network node 2. If network node 1 and network node 2 have different synchronization sources, UE-1 and UE-2 may become out of sync.

[0027] UE 104 can be included in various types of TSN services or TSN time domains. Each TSN time domain is associated with a type of TSN service and a TSN time domain ID. When UE-1 and UE-2 participate in the same type of TSN service or service, or TSN time domain-x or TSN port-y, and a PC5 connection has been established, they can communicate using TSN services through the PC5 interface. UE 104 can maintain at least one TSN time associated with TSN time domain ID-x or TSN port-y. In addition, UE 104 also maintains timing information associated with the radio interface.

[0028] Example 1-1: Network Determination Figure 3An example method 300 for determining network 100 in a unicast scenario is shown. In step 310, a first UE 104 may establish a PC5 link with a second UE 104. In some configurations, the target ID of the PC5 link for the first UE 104 is D1. In step 320, before the first UE 104 reports information to network 100, the first UE 104 may receive the information described in step 310 from the second UE 104. This information may further include: a network 100 indication indicating whether the UE 104 is directly or indirectly synchronizing to a network node or network node identifier; one or more synchronization source type indications indicating the synchronization source type of the UE 104 (e.g., GNSS or network node); and the priority of the synchronization source. The first UE 104 may report the received information and the target ID D1 to network 100.

[0029] In step 325, the first UE 104 may report information to network 100. This information may include clock priority, clock class, clock accuracy, and clock stability (e.g., offset-scaled logarithmic variance). The information may also include a Global Navigation Satellite System (GNSS) indication, indicating whether the UE 104 is directly or indirectly synchronized to GNSS. The information may also include a TSN indication, indicating whether the UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. The TSN indication may indicate whether the clock of the first UE 104 is a TSN timing GM. The information may also include the status of the first UE 104's PTP port (e.g., Leader or Master status, Follower or Slave status).

[0030] In step 330, the first UE 104 may receive synchronization configuration information from network 100. This configuration information includes an indication that UE 104 is a synchronization source for the link associated with target ID D1, or that UE 104 should send synchronization information to the second UE 104 associated with target ID D1. In step 340, if the first UE 104 is configured as a synchronization source or configured to send timing information for the radio interface, then UE 104 may send the timing information for the radio interface to the second UE 104 associated with target ID D1.

[0031] In step 350, the first UE 104 may send timing information of the radio interface to the second UE 104 associated with the target ID D1. The UE 104 may send the timing information of the radio interface periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. The UE 104 may regard the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving a message (such as an SL MIB or S-SSB).

[0032] The timing information from the wireless interface can be used for timestamps. The first UE 104 or the second UE 104 can send directFrameNumber information and S-SSB to network 100. directFrameNumber indicates the frame number for transmitting the S-SSB. The first UE 104 or the second UE 104 can receive directFrameNumber information and S-SSB. directFrameNumber indicates the frame number for transmitting the S-SSB. In this case, the directFrameNumber information and S-SSB can be sent by the third UE 105. The first UE 104 or the second UE 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0033] First UE 104 can send PTP or gPTP messages to second UE 104 and generate an inbound timestamp (TSi) for the PTP or gPTP event (Sync) message. First UE 104 can send PTP or gPTP messages in response to a connection between first UE 104 and the TSN timing GM, a clock corresponding to the TSN timing GM, or a PTP port associated with a Leader or Master state. First UE 104 can receive PTP or gPTP messages from second UE 104 and create an outbound timestamp (TSe) for the PTP or gPTP event (Sync) message using timing information. First UE 104 can receive PTP or gPTP messages from second UE 104 in response to a disconnection from the TSN timing GM, a clock not corresponding to the TSN timing GM, or a PTP port associated with a Follower or Slave state. In step 360, the first UE 104 or the second UE 104 may use the difference between TSi and TSe as the calculated dwell time spent by the PTP or gPTP message within the radio system. Furthermore, the first UE 104 or the second UE 104 may consider whether to update the clock timing information.

[0034] Example 1-2: UE 104 Determined (No Network) Figure 4 An example method 400 for determining UE 104 in the absence of a network in a unicast scenario is shown. In step 410, the first UE 104 may establish a PC5 link with the second UE, and for the first UE 104, the target ID of the PC5 link may be D1. In step 420, capability messages may be exchanged between the first UE 104 and the second UE 104. The capability messages may include whether UE 104 supports sending or receiving timing information. In some configurations, method 400 does not include step 420.

[0035] In step 430, the first UE 104 may receive information from the second UE 104. This information may include any information described in step 435. In some configurations, step 430 may not occur, or may occur after or before step 420. In step 435, the first UE 104 may send information to the second UE 104. This information may include clock priority, clock class, clock accuracy, and clock stability (e.g., offset-scaled logarithmic variance). This information may also include a Global Navigation Satellite System (GNSS) indication indicating whether the UE 104 is directly or indirectly synchronized to GNSS. This information may also include a TSN indication indicating whether the UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. This indication may indicate whether the clock of the first UE 104 is a TSN timing GM. This information may also include the status of the first UE's PTP port (e.g., Leader or Master status, Follower or Slave status). This information may also include: a network 100 indication indicating whether UE 104 is directly or indirectly synchronizing to a network node or network node identifier; one or more synchronization source indications indicating the synchronization source of UE 104 (e.g., GNSS or a network node); and the priority of the synchronization source. The first UE 104 may report the received information and target ID D1 to network 100.

[0036] If the clock or synchronization source priority of the first UE 104 is equal to the clock or synchronization source priority of the second UE 104, and the clock level of the first UE 104 is higher than the clock level of the second UE 104, then the first UE 104 can determine to send timing information to the second UE 104. If the clock or synchronization source priority of the first UE 104 is equal to the clock or synchronization source priority of the second UE, the clock level of the first UE 104 is equal to the clock level of the second UE, and the clock precision of the first UE 104 is higher than the clock precision of the second UE, then the first UE 104 can determine to send timing information to the second UE 104. If the clock or synchronization source priority of the first UE 104 is equal to that of the second UE 104, the clock class of the first UE 104 is equal to that of the second UE 104, the clock precision of the first UE 104 is equal to that of the second UE 104, and the clock stability of the first UE 104 is higher than that of the second UE 104, then the first UE 104 can determine whether to send timing information to the second UE 104. Otherwise, the first UE 104 will not send timing information to the second UE 104.

[0037] If the synchronization source of the first UE 104 and the second UE 104 is the same, then neither the first UE 104 nor the second UE 104 needs to send timing information to the network 100. Alternatively, both the first UE 104 and the second UE 104 can use their own timing information.

[0038] In step 440, the first UE 104 may determine whether to send timing information to the second UE 104. The first UE 104 may determine to send timing information to the second UE 104 in response to one or more conditions being met. These conditions may include: if the first UE 104 can support sending timing information and the second UE 104 can support receiving timing information; if the clock priority of the first UE 104 is higher than the clock priority of the second UE; if the clock class of the first UE 104 is higher than the clock class of the second UE; or if the clock precision of the first UE 104 is higher than the clock precision of the second UE 104.

[0039] These conditions may also include: if the clock stability of the first UE 104 is higher than that of the second UE; if the first UE 104 is directly synchronized to GNSS; if the first UE 104 is directly synchronized to a network node; if the first UE 104 is connected to the TSN controller or TSN GM clock via a wired or wireless connection; or if the clock of the first UE 104 is a TSN timing GM. These conditions may also include: if the PTP port of the first UE 104 is configured in Leader or Master state for use in the link between the first UE 104 and the second UE; if the PTP port of the first UE 104 is configured in Leader or Master state for use with the target ID D1 associated with the link between the first UE 104 and the second UE; if the synchronization source priority of the first UE 104 is higher than that of the second UE; or if the synchronization sources of the first UE 104 and the second UE 104 are different.

[0040] In step 450, the first UE 104, associated with the target ID D1, may send timing information of the radio interface to the second UE 104. The UE 104 may send the timing information of the radio interface periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may also include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. The UE 104 may consider the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving the message.

[0041] Timing information for the wireless interface can use timestamps. The first UE 104 or the second UE 104 can send directFrameNumber information and S-SSB to network 100. directFrameNumber can indicate the frame number of the transmitted S-SSB. In one embodiment, the first UE 104 or the second UE 104 can receive directFrameNumber information and S-SSB. directFrameNumber can indicate the frame number of the transmitted S-SSB. In this case, directFrameNumber information and S-SSB can be sent by a third UE 104. In one embodiment, the first UE 104 or the second UE 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0042] First UE 104 can send PTP or gPTP messages to second UE 104 and generate an inbound timestamp (TSi) for the PTP or gPTP event (Sync) message. First UE 104 can send PTP or gPTP messages in response to a connection between first UE 104 and the TSN timing GM, a clock corresponding to the TSN timing GM, or a PTP port associated with a Leader or Master state. First UE 104 can receive PTP or gPTP messages from second UE 104 and create an outbound timestamp (TSe) for the PTP or gPTP event (Sync) message using timing information. First UE 104 can receive PTP or gPTP messages from second UE 104 in response to a disconnection from the TSN timing GM, a clock not corresponding to the TSN timing GM, or a PTP port associated with a Follower or Slave state. In step 460, the first UE 104 or the second UE 104 may use the difference between TSi and TSe as the calculated dwell time spent by the PTP or gPTP message within the radio system. Furthermore, the first UE 104 or the second UE 104 may consider whether to update the clock timing information.

[0043] Examples 1-3: UE 104 Determination (Network Assistance) Figure 5An example method for determining UE 104 in a network context for unicast scenarios is shown. In step 510, the first UE 104 may establish a PC5 link with the second UE 104. In some configurations, the target ID of the PC5 link for the first UE 104 is D1. In step 520, the first UE 104 may report information to network 100. This information may include clock priority, clock class, clock accuracy, and clock stability (e.g., offset-scaled logarithmic variance). This information may also include a Global Navigation Satellite System (GNSS) indication indicating whether UE 104 is directly or indirectly synchronized to GNSS. This information may also include a Time-Sensitive Network (TSN) indication indicating whether UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. This indication may indicate whether the clock of the first UE 104 is a TSN timing GM. This information may also include the status of the first UE's PTP port (e.g., Leader or Master status, Follower or Slave status).

[0044] In step 530, the first UE 104 can receive synchronization configuration information from network 100. This configuration information includes the priority of the synchronization source or clock, the synchronization source identifier, or the synchronization source type (e.g., GNSS or network node). In step 540, the first UE 104 can receive the priority of synchronization information from the second UE 104. In some configurations, step 545 may not occur. In step 545, the first UE 104 can send the priority of the synchronization information to the second UE 104. The synchronization information may be the same as the configuration information. In step 550, the first UE 104 can determine whether to send timing information to the second UE 104. If the synchronization source priority of the first UE 104 is higher than that of the second UE 104, if the synchronization source identifiers of the first UE 104 and the second UE 104 are different, or if the synchronization source types of the first UE 104 and the second UE 104 are different, then the first UE 104 can send timing information to the second UE 104. Otherwise, the first UE 104 will not send timing information to the second UE 104.

[0045] If the synchronization source identifiers of the first UE 104 and the second UE 104 are the same, then neither the first UE 104 nor the second UE 104 needs to send timing information. Alternatively, both the first UE 104 and the second UE 104 can use their respective timing information. The first UE 104 can receive and use timing information from the second UE 104. In step 560, the first UE 104 can send radio interface timing information to the second UE 104 associated with the target IDD1. The UE 104 can send the radio interface timing information periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. The UE 104 can consider the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving the message.

[0046] Timing information for the wireless interface can use timestamps. The first UE 104 or the second UE 104 can send directFrameNumber information and S-SSB to network 100. directFrameNumber can indicate the frame number of the transmitted S-SSB. In one embodiment, the first UE 104 or the second UE 104 can receive directFrameNumber information and S-SSB. directFrameNumber can indicate the frame number of the transmitted S-SSB. In this case, directFrameNumber information and S-SSB can be sent by a third UE 104. The first UE 104 or the second UE 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0047] The first UE 104 can receive PTP or gPTP messages from the second UE 104 and create an outbound timestamp (TSe) for the PTP or gPTP event (Sync) message using timing information. In response to the first UE 104 disconnecting from the TSN timing GM, the first UE 104's clock not corresponding to the TSN timing GM, or the first UE 104's PTP port being associated with a Follower or Slave state, the first UE 104 can receive PTP or gPTP messages from the second UE 104. The first UE 104 can send PTP or gPTP messages to the second UE 104 and generate an inbound timestamp (TSi) for the PTP or gPTP event (Sync) message. In response to the first UE 104 connecting to the TSN timing GM, the first UE 104's clock corresponding to the TSN timing GM, or the first UE 104's PTP port being associated with a Leader or Master state, the first UE 104 can send PTP or gPTP messages. In step 570, the first UE 104 or the second UE 104 may use the difference between TSi and TSe as the calculated dwell time spent by the PTP or gPTP message within the radio system. Furthermore, the first UE 104 or the second UE 104 may consider whether to update the clock timing information.

[0048] For TSN-type service communication, an important aspect is that the communicating UEs can synchronize with each other. According to existing technology, UE 104 can obtain synchronization information from network 100. However, there is no solution to keep different UEs synchronized with each other. For example, UE-1 and UE-2 are in the same group associated with target ID-D2 and perform sidelink multicast communication to transmit TSN-type services. UE-1 can obtain time information from network node 1, and UE-2 can obtain time information from network node 2. If network node 1 and network node 2 include different source synchronization clocks, UE-1 and UE-2 may be out of sync. This disclosure includes several solutions for how UE 104 determines the synchronization source and how to send synchronization information.

[0049] UE 104 can participate in various types of TSN services or TSN time domains. Each TSN time domain can be associated with a type of TSN service and a TSN time domain ID. UE-1 and UE-2 can be in the same type of TSN service, service, TSN time domain-x, or TSN port-y. UE-1 and UE-2 can establish PC5 connections for multicast and can communicate using TSN services. UE 104 can maintain at least one TSN time associated with TSN time domain ID-x or TSN port-y. UE 104 can maintain timing information associated with the radio interface.

[0050] Example 2-1: Network Determination Figure 6 An example method 600 for determining a network in a multicast scenario is illustrated. In step 610, a first UE 104 may establish a multicast sidelink with one or more second UEs 104, and the target ID of the multicast sidelink is D2. In step 620, the first UE 104 may send information to one or more second UEs 104. This information may include clock priority, clock class, clock accuracy, or clock stability (e.g., offset-scaled logarithmic variance). This information may also include a GNSS indication indicating whether the UE 104 is directly or indirectly synchronized to GNSS. This information may also include a TSN indication indicating whether the UE 104 is connected to a TSN controller or a TSN GM clock via a wired or wireless connection. This indication may indicate that the clock of the first UE 104 is a TSN timing GM. This information may also include the status of the first UE 104's PTP port (e.g., Leader or Master status, Follower or Slave status). This information may also include a multicast header indication indicating whether the UE 104 is the multicast header for the target D2.

[0051] In step 630, the first UE 104 may receive synchronization configuration information from the network 100. This configuration information includes indications that the UE 104 is the synchronization source of the link associated with target ID D2, or that the UE 104 should send synchronization information to one or more second UEs 104 associated with target ID D2.

[0052] In step 640, if the first UE 104 is configured as a synchronization source or configured to transmit timing information of the radio interface, then the UE 104 may transmit the timing information of the radio interface to one or more second UEs 104 associated with the target ID D2.

[0053] In step 650, the first UE 104 may send timing information of the radio interface to one or more second UEs 104 associated with the target ID D2. The UE 104 may send the timing information of the radio interface periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. The UE 104 may regard the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving the message.

[0054] Timing information for the wireless interface can use timestamps. A first UE 104 or one or more second UEs 104 can send directFrameNumber information and an S-SSB to network 100. The directFrameNumber can indicate the frame number of the transmitted S-SSB. A first UE 104 or one or more second UEs 104 can receive the directFrameNumber information and the S-SSB. The directFrameNumber can indicate the frame number of the transmitted S-SSB. In this case, the directFrameNumber information and the S-SSB can be sent by a third UE 104. The first UE 104 or one or more second UEs 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0055] The first UE 104 can send PTP or gPTP messages to one or more second UEs 104 and generate an inbound timestamp (TSi) for the PTP or gPTP event (Sync) message. The first UE 104 can send PTP or gPTP messages in response to the first UE 104 being connected to the TSN timing GM, the first UE 104's clock corresponding to the TSN timing GM, or the first UE 104's PTP port being associated with a Leader or Master state. The first UE 104 can receive PTP or gPTP messages from one or more second UEs 104 and create an outbound timestamp (TSe) for the PTP or gPTP event (Sync) message using timing information. The first UE 104 can receive PTP or gPTP messages from one or more second UEs 104 in response to the first UE 104 being disconnected from the TSN timing GM, the first UE 104's clock not corresponding to the TSN timing GM, or the first UE 104's PTP port being associated with a Follower or Slave state. In step 660, the first UE 104 or one or more second UEs 104 may use the difference between TSi and TSe as the calculated dwell time spent by the PTP or gPTP message within the radio system. Furthermore, the first UE 104 or one or more second UEs 104 may consider whether to update the clock timing information.

[0056] Example 2-2: UE AS Layer Determination Figure 7An example method 700 for determining the AS layer of UE 104 in a multicast scenario is illustrated. In step 710, the first UE 104 may establish a multicast side link with one or more second UE 104s, and the target ID of the multicast side link is D2. In step 720, the first UE 104 may receive information from one or more second UE 104s. This information may include clock priority, clock class, clock accuracy, and clock stability (e.g., offset-scaled logarithmic variance). This information may also include a GNSS indication indicating whether UE 104 is directly or indirectly synchronized to GNSS. This information may also include a Time-Sensitive Network (TSN) indication indicating whether UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. This indication may indicate whether the clock of the first UE 104 is a TSN timing GM, or the information may include the status of the first UE 104's PTP port (e.g., Leader or Master status, Follower or Slave status), or the information may include a multicast header indication to indicate whether UE 104 is the multicast header of the target D2. In some configurations, step 720 may not occur.

[0057] In step 730, the first UE 104 may send information to one or more second UEs 104. This information may include clock priority, clock class, clock accuracy, and clock stability (e.g., offset-scaled logarithmic variance). This information may include a GNSS indication indicating whether the UE 104 is directly or indirectly synchronized to GNSS. This information may include a Time-Sensitive Network (TSN) indication indicating whether the UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. This indication may indicate whether the clock of the first UE 104 is a TSN timing GM. This information may include the status of the first UE 104's PTP port (e.g., Leader or Master status, Follower or Slave status) and a multicast header indication indicating whether the UE 104 is the multicast header for the target D2.

[0058] In step 740, the first UE 104 may determine whether to send timing information to one or more second UEs 104. In response to satisfying one or more conditions, the first UE 104 determines to send timing information to one or more second UEs 104. These conditions may include: if the first UE 104 is the head UE 104, the clock priority of the first UE 104 is higher than the clock priority of one or more second UEs 104, the clock class of the first UE 104 is higher than the clock class of one or more second UEs 104, or the clock precision of the first UE 104 is higher than the clock precision of one or more second UEs 104.

[0059] These conditions may also include: if the clock stability of the first UE 104 is higher than the clock stability of one or more second UEs 104; if the first UE 104 is directly synchronized to GNSS; if the first UE 104 is directly synchronized to a network node; if the first UE 104 is connected to the TSN controller or TSN GM clock via a wired or wireless connection; or if the clock of the first UE 104 is a TSN timing GM. These conditions may also include: if the PTP port of the first UE 104 is configured in Leader or Master state for use in the link between the first UE 104 and one or more second UEs; if the PTP port of the first UE 104 is configured in Leader or Master state for use with the target ID D2 associated with the link between the first UE 104 and one or more second UEs; if the synchronization source priority of the first UE 104 is higher than the synchronization source priority of one or more second UEs; or if the synchronization sources of the first UE 104 and one or more second UEs 104 are different.

[0060] If the clock or synchronization source priority of the first UE 104 is equal to the clock or synchronization source priority of one or more second UEs 104, and the clock level of the first UE 104 is higher than the clock level of one or more second UEs 104, then the first UE 104 can determine to send timing information to one or more second UEs 104. If the clock or synchronization source priority of the first UE 104 is equal to the clock or synchronization source priority of one or more second UEs 104, the clock level of the first UE 104 is equal to the clock level of one or more second UEs 104, and the clock precision of the first UE 104 is higher than the clock precision of one or more second UEs 104, then the first UE 104 can determine to send timing information to one or more second UEs 104. If the clock or synchronization source priority of the first UE 104 is equal to the clock or synchronization source priority of one or more second UEs 104, the clock class of the first UE 104 is equal to the clock class of one or more second UEs 104, the clock precision of the first UE 104 is equal to the clock precision of one or more second UEs 104, and the clock stability of the first UE 104 is higher than the clock stability of one or more second UEs 104, then the first UE 104 can determine to send timing information to one or more second UEs 104. Otherwise, the first UE 104 will not send timing information to one or more second UEs 104.

[0061] If the synchronization source of the first UE 104 and one or more second UEs 104 is the same, then neither the first UE 104 nor one or more second UEs 104 may send timing information. Alternatively, the first UE 104 and one or more second UEs 104 may use their respective timing information. In step 750, the first UE 104 may send radio interface timing information to one or more second UEs 104 associated with target ID D2. UE 104 may send radio interface timing information periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. UE 104 may consider the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving the message.

[0062] Timing information for the wireless interface can use timestamps. A first UE 104 or one or more second UEs 104 can send directFrameNumber information and an S-SSB to network 100. The directFrameNumber can indicate the frame number of the transmitted S-SSB. A first UE 104 or one or more second UEs 104 can receive the directFrameNumber information and the S-SSB. The directFrameNumber can indicate the frame number of the transmitted S-SSB. In this case, the directFrameNumber information and the S-SSB can be sent by a third UE 104. The first UE 104 or one or more second UEs 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0063] Example 2-3: UE NAS Layer Determination Figure 8An example method 800 for determining the NAS layer of UE 104 in a multicast scenario is illustrated. In step 810, the first UE 104 may establish a multicast side link with one or more second UE 104s, and the target ID of the multicast side link is D2. In step 820, the AS layer of the first UE 104 may obtain information from the NAS layer of the first UE 104. This information may include a multicast header indication indicating that UE 104 is the multicast header for target D2, or a TSN indication indicating that UE 104 is connected to a TSN controller or TSN GM clock via a wired or wireless connection. The TSN indication may indicate that the clock of the first UE 104 is a TSN timing GM. This information may include the status of the first UE 104's PTP port (e.g., Leader or Master status, Follower or Slave status), or that the first UE 104 is a synchronization source.

[0064] In step 830, the first UE 104 may determine whether to send timing information to one or more second UEs 104. In response to satisfying one or more conditions, the first UE 104 determines to send timing information to one or more second UEs 104. These conditions may include: if the first UE 104 is the head UE 104, the first UE 104 is the synchronization source, the first UE 104 is connected to the TSN controller or TSN GM clock via a wired or wireless connection, or the clock of the first UE 104 is the TSN timing GM. These conditions may also include: if the PTP port of the first UE 104 is configured in Leader or Master state for use in the link between the first UE 104 and one or more second UEs 104, and the PTP port of the first UE 104 is configured in Leader or Master state for use in the target ID D2 associated with the link between the first UE 104 and one or more second UEs 104.

[0065] In step 840, the first UE 104 may send timing information of the radio interface to one or more second UEs 104 associated with the target ID D2. The UE 104 may send the timing information of the radio interface periodically or when the timing information changes. The timing information may include a referenceSFN field. The referenceSFN field may correspond to reference time information. The timing information may include a referenceTimeInfo field. The referenceTimeInfo field may indicate the time at the termination boundary of the system frame indicated by the referenceSFN field. The UE 104 may regard the frame (indicated by the referenceSFN) as the frame (past or future) closest to receiving the message.

[0066] Timing information for the wireless interface can use timestamps. A first UE 104 or one or more second UEs 104 can send directFrameNumber information and an S-SSB to network 100. The directFrameNumber can indicate the frame number of the transmitted S-SSB. A first UE 104 or one or more second UEs 104 can receive the directFrameNumber information and the S-SSB. The directFrameNumber can indicate the frame number of the transmitted S-SSB. In this case, the directFrameNumber information and the S-SSB can be sent by a third UE 104. The first UE 104 or one or more second UEs 104 can determine the frame number based on GPS time, Coordinated Universal Time (UTC), or local time.

[0067] Figure 9 A flowchart 900 is shown for performing sidelink communication for a time-sensitive network. Method 900 can use a combination of... Figure 1-2 The method 900 may be performed by any one or more of the detailed components and devices. In summary, in some embodiments, method 900 may be performed by a wireless communication node (e.g., base station (BS) 102). Depending on the embodiment, additional, fewer, or different operations may be performed in method 900. At least one aspect of the operation relates to a system, method, apparatus, or computer-readable medium.

[0068] The wireless communication method may include: a first wireless communication device sending a message to a second wireless communication device, the message including timing configuration auxiliary information for sidelink communication. The wireless communication method may also include: the first wireless communication device receiving timing configuration information from a network (e.g., network 100). The timing configuration auxiliary information associated with a first clock of the first wireless communication device may include at least one of the following: priority of the first clock, class of the first clock, accuracy of the first clock, stability of the first clock, Global Navigation Satellite System (GNSS) indication, Time-Sensitive Network (TSN) indication, status of the Precision Time Protocol (PTP) port of the first wireless communication device, or multicast header indication.

[0069] The timing configuration information may include at least one of the following: whether the first wireless communication device can act as a source clock and send timing-related information to one or more other wireless communication devices, the priority of the first clock of the first wireless communication device, the identifier of the first clock, or the type of the first clock. The wireless communication method may include: the first wireless communication device receiving timing configuration information, timing configuration auxiliary information, or a first capability message from a second wireless communication device. The first capability message includes whether the second wireless communication device supports sending or receiving timing information. The wireless communication method may include: the first wireless communication device sending timing configuration information, timing configuration auxiliary information, or a second capability message to the second wireless communication device. The second capability message includes whether the first wireless communication device supports sending or receiving timing information. The wireless communication method may include: the first wireless communication device sending either the received timing configuration information or timing configuration auxiliary information to the network.

[0070] The wireless communication method may include: in response to satisfying at least one of the following conditions, a first wireless communication device determines a source clock and transmits timing-related information to one or more other wireless communication devices. These conditions include: the first wireless communication device supports sending timing configuration information and the second wireless communication device supports receiving timing configuration information; the first wireless communication device is a head user equipment (UE); the priority of the first clock is higher than the priority of the second clock associated with the second communication device; the class of the first clock is higher than the class of the second clock; the accuracy of the first clock is higher than the accuracy of the second clock; the stability of the first clock is higher than the stability of the second clock; the first wireless communication device is directly synchronized to GNSS; the first wireless communication device is directly synchronized to a network node; the first wireless communication device is connected to the TSN controller or TSN GM clock via a wired or wireless connection; the first clock is the TSN timing GM; the PTP port is configured in Leader or Master state for sidelink communication between the first and second wireless communication devices; the PTP port is configured in Leader or Master state for source / target ID associated with sidelink communication between the first and second wireless communication devices; the synchronization source priority of the first wireless communication device is higher than the synchronization source priority of the second wireless communication device; the synchronization source of the first wireless communication device is different from the synchronization source of the second wireless communication device; the type of the synchronization source of the first wireless communication device is different from the type of the synchronization source of the second wireless communication device; or the identifier of the synchronization source of the first wireless communication device is different from the identifier of the synchronization source of the second wireless communication device.

[0071] The wireless communication method may include: the AS layer of a first wireless communication device obtaining at least one of the following information from its NAS layer: multicast indication, TSN indication, the status of the PTP port of the first wireless communication device, or the wireless communication device being a synchronization source. The wireless communication method may include: in response to at least one of the following conditions, the first wireless communication device determines to send timing configuration information to the second wireless communication device: the first wireless communication device is a head UE, the first wireless communication device is a synchronization source, the first wireless communication device is connected to a TSN controller or TSN GM clock via a wired or wireless connection, the first clock is a TSN timing GM, or the PTP port is configured in a Leader or Master state for target ID D2.

[0072] The wireless communication method may include a first wireless communication device transmitting wireless interface-related information including either a referenceSFN or a referenceTimeInfo. The wireless interface-related information is used to determine a timestamp. The wireless interface-related information is carried by a sidelink RRC message. The first wireless communication device periodically transmits the wireless interface-related information. In response to recognizing a change in any of the wireless interface-related information, the first wireless communication device transmits timing configuration information.

[0073] The wireless communication method may include: a first wireless communication device determining itself as a source clock and transmitting timing-related information to one or more other wireless communication devices. Before determining itself as a source clock, the first wireless communication device receives a message from a second wireless communication device, the message including timing configuration assistance information, timing configuration information, or a first capability message. The first capability message includes whether the second wireless communication device supports transmitting or receiving timing-related information.

[0074] The wireless communication method may include, in response to at least one of the following conditions, a first wireless communication device determines itself as a source clock and transmits timing-related information to one or more other wireless communication devices: the first wireless communication device supports transmitting timing configuration information and the second wireless communication device supports receiving timing configuration information; the first wireless communication device is a head user equipment (UE); the first clock has a higher priority than a second clock associated with the second communication device; the first clock has a higher class than the second clock; the first clock has higher accuracy than the second clock; the first clock has higher stability than the second clock; the first wireless communication device is directly synchronized to GNSS; the first wireless communication device is directly synchronized to a network node; and the first wireless communication device is connected to a TSN controller or TSN via a wired or wireless connection. The GM clock connection is used, with the first clock being the TSN timing GM. The PTP port is configured in Leader or Master state for sidelink communication between the first and second wireless communication devices. The PTP port is also configured in Leader or Master state for the source / target ID associated with the sidelink communication between the first and second wireless communication devices. The synchronization source of the first wireless communication device has a higher priority than the synchronization source of the second wireless communication device. The synchronization sources of the first and second wireless communication devices are different, the types of the synchronization sources of the first and second wireless communication devices are different, or the identifiers of the synchronization sources of the first and second wireless communication devices are different.

[0075] The wireless communication method may include, in response to at least one of the following conditions, a first wireless communication device determining itself as a source clock and sending timing-related information to one or more other wireless communication devices: the first wireless communication device is a head UE; the first wireless communication device is a synchronization source; the first wireless communication device is connected to a TSN controller or TSN GM clock via wired or wireless communication; the clock of the first wireless communication device is connected to the TSN timing GM; or the PTP port of the first wireless communication device is configured in a Leader or Master state for use with target ID D2. The wireless communication method may include the first wireless communication device sending wireless interface-related information including referenceSFN or referenceTimeInfo. The wireless interface-related information is used to determine a timestamp.

[0076] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functionality of the present solution. However, those skilled in the art will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, those skilled in the art will understand that one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative embodiments described above.

[0077] It should also be understood that any reference to elements using designations such as "first," "second," etc., herein does not generally limit the number or order of these elements. Rather, these designations are used herein as a convenient means of distinguishing between two or more elements or multiple instances of a single element. Therefore, references to first and second elements do not imply that only two elements can be used, nor do they imply that the first element must somehow precede the second element.

[0078] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0079] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of function. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0080] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs), including general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may further include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

[0081] If implemented in software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium capable of transferring a computer program or code from one place to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and accessible to a computer.

[0082] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0083] Additionally, in embodiments of this solution, memory or other storage devices and communication components may be employed. It should be understood that, for clarity, embodiments of this solution have been described above with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without departing from this solution. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means of providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0084] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A wireless communication method, comprising: The first wireless communication device sends a message, the message including timing configuration auxiliary information for sidelink communication, and The first wireless communication device receives timing configuration information from the network.

2. The wireless communication method as described in claim 1, wherein, The timing configuration assistance information associated with the first clock of the first wireless communication device may include at least one of the following: The priority of the first clock, The level of the first clock, The accuracy of the first clock, The stability of the first clock, Global Navigation Satellite System (GNSS) indication, Time-Sensitive Networking (TSN) indication, The status of the Precision Time Protocol (PTP) port of the first wireless communication device, or Multicast head instructions.

3. The wireless communication method as described in claim 1, wherein, The timing configuration information may include at least one of the following: Whether the first wireless communication device can act as a source clock and send timing-related information to one or more other wireless communication devices. The priority of the first clock of the first wireless communication device. The first clock's markings, or The type of the first clock.

4. The wireless communication method as described in claim 2, further comprising: The first wireless communication device receives the timing configuration information, the timing configuration auxiliary information, or the first capability message from the second wireless communication device. The first capability message includes whether the second wireless communication device supports sending or receiving timing information.

5. The wireless communication method as described in claim 2, further comprising: The first wireless communication device sends the timing configuration information, the timing configuration auxiliary information, or the second capability message to the second wireless communication device. The second capability message includes whether the first wireless communication device supports sending or receiving timing information.

6. The wireless communication method as described in claim 4, further comprising: The first wireless communication device sends either the received timing configuration information or the timing configuration auxiliary information to the network.

7. The wireless communication method according to any one of claims 1 to 5, further comprising: In response to at least one of the following conditions being met, the first wireless communication device determines itself as the source clock and sends timing-related information to one or more other wireless communication devices: The first wireless communication device supports sending the timing configuration information, and the second wireless communication device supports receiving the timing configuration information. The first wireless communication device is a head user equipment (UE). The first clock has a higher priority than the second clock associated with the second wireless communication device. The first clock has a higher priority than the second clock. The accuracy of the first clock is higher than that of the second clock. The stability of the first clock is higher than that of the second clock. The first wireless communication device directly synchronizes with GNSS. The first wireless communication device directly synchronizes with the network node. The first wireless communication device is connected to the TSN controller or TSN GM clock via a wired or wireless connection. The first clock is the TSN timing GM. The PTP port is configured in Leader or Master state for sidelink communication between the first wireless communication device and the second wireless communication device. The PTP port is configured in Leader or Master state and is used for the source / target ID associated with sidelink communication between the first wireless communication device and the second wireless communication device. The synchronization source priority of the first wireless communication device is higher than that of the synchronization source priority of the second wireless communication device. The synchronization source of the first wireless communication device is different from the synchronization source of the second wireless communication device. The type of synchronization source of the first wireless communication device is different from the type of synchronization source of the second wireless communication device, or The identifier of the synchronization source of the first wireless communication device is different from the identifier of the synchronization source of the second wireless communication device.

8. The wireless communication method as described in claim 1, further comprising: The AS layer of the first wireless communication device obtains at least one of the following information from the NAS layer of the first wireless communication device: Multicast instructions TSN indication, The status of the PTP port of the first wireless communication device, or The wireless communication device is a synchronization source.

9. The wireless communication method according to any one of claims 1 to 3, further comprising: In response to at least one of the following conditions, the first wireless communication device determines to send the timing configuration information to the second wireless communication device: The first wireless communication device is a UE (User Equipment). The first wireless communication device is a synchronization source. The first wireless communication device is connected to the TSN controller or TSN GM clock via a wired or wireless connection. The first clock is TSN timing GM, or The PTP port is configured in Leader or Master state for target ID D2.

10. The wireless communication method as described in claim 1, further comprising: The first wireless communication device transmits wireless interface related information including at least one of the following: referenceSFN or referenceTimeInfo.

11. The wireless communication method as described in claim 10, wherein, The wireless interface information is used to determine the timestamp.

12. The wireless communication method as described in claim 10, wherein, The wireless interface-related information is carried by the sidelink RRC message.

13. The wireless communication method as described in claim 10, wherein, The first wireless communication device periodically transmits information related to the wireless interface.

14. The wireless communication method as described in claim 10, wherein, In response to detecting a change in either the wireless interface-related information or the timing information, the first wireless communication device sends the timing configuration information.

15. A wireless communication method, comprising: The first wireless communication device determines the source clock and sends timing-related information to one or more other wireless communication devices.

16. The wireless communication method of claim 15, further comprising, before determining the source clock: The first wireless communication device receives from the second wireless communication device a message including: timing configuration assistance information, timing configuration information, or a first capability message, wherein the first capability message includes whether the second wireless communication device supports sending or receiving the timing-related information.

17. The wireless communication method as described in claim 15 or 16, further comprising: In response to at least one of the following conditions being met, the source clock is determined, and the timing-related information is transmitted to the one or more other wireless communication devices: The first wireless communication device supports sending the timing configuration information, and the second wireless communication device supports receiving the timing configuration information. The first wireless communication device is a head user equipment (UE). The first clock has a higher priority than the second clock associated with the second communication device. The first clock has a higher priority than the second clock. The accuracy of the first clock is higher than that of the second clock. The stability of the first clock is higher than that of the second clock. The first wireless communication device directly synchronizes with GNSS. The first wireless communication device directly synchronizes with the network node. The first wireless communication device is connected to the TSN controller or TSN GM clock via a wired or wireless connection. The first clock is the TSN timing GM. The PTP port is configured in Leader or Master state for sidelink communication between the first wireless communication device and the second communication device. The PTP port is configured in Leader or Master state and is used for the source / target ID associated with sidelink communication between the first wireless communication device and the second communication device. The synchronization source priority of the first wireless communication device is higher than that of the synchronization source priority of the second wireless communication device. The synchronization source of the first wireless communication device is different from the synchronization source of the second wireless communication device. The type of synchronization source of the first wireless communication device is different from the type of synchronization source of the second wireless communication device, or The identifier of the synchronization source of the first wireless communication device is different from the identifier of the synchronization source of the second wireless communication device.

18. The wireless communication method as described in claim 15 or 16, further comprising: In response to at least one of the following conditions being met, the source clock is determined, and the timing-related information is transmitted to the one or more other wireless communication devices: The first wireless communication device is a UE (User Equipment). The first wireless communication device is a synchronization source. The first wireless communication device has communicated with the TSN controller or the TSN GM clock via wired or wireless communication. The clock of the first wireless communication device is connected to the TSN timing GM, or The PTP port of the first wireless communication device is configured in Leader or Master state for target ID D2.

19. The wireless communication method as described in claim 15, further comprising: The first wireless communication device transmits wireless interface related information including the following: referenceSFN and referenceTimeInfo.

20. The wireless communication method as described in claim 19, wherein, The wireless interface information is used to determine the timestamp.

21. A wireless communication method, comprising: The network sends timing configuration information to the first wireless communication device.

22. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method as claimed in any one of claims 1 to 20.

23. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method as described in any one of claims 1 to 20.

Images