Methods, apparatuses, and systems for timing alignment

Abstract

The present application relates to a communication method and a communication device. An exemplary method comprises: receiving a timestamp indication indicating a transmission time of a downlink (DL) signal; determining a timing advance (TA) based on a reception time of the DL signal and the timestamp indication; and transmitting an uplink (UL) signal according to the determined TA.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 573,235, filed April 2, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application generally relates to wireless communication. In particular, it relates to a method, apparatus, and system for timing alignment. Background Technology

[0003] Wireless communication systems such as fourth-generation (4G) systems (e.g., long-term evolution (LTE) systems) and fifth-generation (5G) systems (e.g., new radio (NR) systems) have been deployed to provide various types of applications, such as messaging, voice, video, and other data. Summary of the Invention

[0004] One or more implementations of this application provide a communication method and a communication apparatus. The techniques described in this application can improve the performance of the TA process.

[0005] According to a first aspect, a method is provided. The method includes: receiving a timestamp indication indicating the transmission time of a downlink (DL) signal. The method further includes: determining a timing advance (TA) based on the reception time of the DL signal and the timestamp indication. The method further includes: transmitting an uplink (UL) signal according to the determined TA.

[0006] In conjunction with the first aspect, in some implementations, the DL signal includes cell common control signaling, group common control signaling, or UE-specific control signaling.

[0007] In conjunction with the first aspect, in some implementations, the DL signaling includes paging messages.

[0008] In conjunction with the first aspect, in some implementations, the DL signal includes DL data services.

[0009] In conjunction with the first aspect, in some implementations, the timestamp indication is included in the DL signal.

[0010] In conjunction with the first aspect, in some implementations, the timestamp indication is included in another DL signal that is different from the DL signal.

[0011] In conjunction with the first aspect, in some implementations, the timestamp indication includes an absolute time value.

[0012] In conjunction with the first aspect, in some implementations, the timestamp indication includes a relative time value.

[0013] In conjunction with the first aspect, in some implementations, the method further includes: receiving a configuration of the timestamp indication. The configuration of the timestamp indication includes an indication of a reference time boundary applied to the timestamp indication.

[0014] In conjunction with the first aspect, in some implementations, the step of determining the TA based on the reception time of the DL signal and the timestamp indication includes: determining the one-way propagation delay based on the reception time of the DL signal and the timestamp indication; and determining the TA based on the one-way propagation delay.

[0015] In conjunction with the first aspect, in some implementations, the TA is also determined based on a timing offset.

[0016] In conjunction with the first aspect, in some implementations, the method further includes: sending a second timestamp indication indicating the transmission time of the UL signal.

[0017] According to a second aspect, a method is provided. The method includes: transmitting a timestamp indication indicating the transmission time of a downlink (DL) signal. The method further includes: receiving an uplink (UL) signal transmitted based on the timestamp indication.

[0018] In conjunction with the second aspect, in some implementations, the DL signal includes cell common control signaling, group common control signaling, or UE-specific control signaling.

[0019] In conjunction with the second aspect, in some implementations, the DL signaling includes paging messages.

[0020] In conjunction with the second aspect, in some implementations, the DL signal includes DL data services.

[0021] In conjunction with the second aspect, in some implementations, the timestamp indication is included in the DL signal.

[0022] In conjunction with the second aspect, in some implementations, the timestamp indication is included in another DL signal that is different from the DL signal.

[0023] In conjunction with the second aspect, in some implementations, the timestamp indication includes an absolute time value.

[0024] In conjunction with the second aspect, in some implementations, the timestamp indication includes a relative time value.

[0025] In conjunction with the second aspect, in some implementations, the method further includes: sending a configuration for the timestamp indication. The configuration for the timestamp indication includes an indication of a reference time boundary applied to the timestamp indication.

[0026] In conjunction with the second aspect, in some implementations, the method further includes: receiving a second timestamp indication indicating the transmission time of the UL signal.

[0027] According to a third aspect, a communication device is provided. The communication device is used to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.

[0028] In conjunction with the third aspect, in some implementations, the communication device includes: a receiving unit for receiving a timestamp indication indicating the transmission time of a downlink (DL) signal. The communication device further includes: a determining unit for determining a timing advance (TA) based on the reception time of the DL signal and the timestamp indication. The communication device further includes: a transmitting unit for transmitting an uplink (UL) signal according to the determined TA.

[0029] In conjunction with the third aspect, in some implementations, the communication device includes: a transmitting unit for transmitting a timestamp indication indicating the transmission time of a downlink (DL) signal. The communication device further includes: a receiving unit for receiving an uplink (UL) signal transmitted based on the timestamp indication.

[0030] In conjunction with the third aspect, in some implementations, the communication device includes one or more processors and interface circuitry. The interface circuitry is used to receive a timestamp indication indicating the transmission time of a downlink (DL) signal. The communication device further includes one or more processors for determining a timing advance (TA) based on the reception time of the DL signal and the timestamp indication. The interface circuitry is used to transmit an uplink (UL) signal according to the determined TA. In some of these implementations, the interface circuitry includes one or more transceivers.

[0031] In conjunction with the third aspect, in some implementations, the communication device includes one or more processors and interface circuitry. The interface circuitry is used to transmit a timestamp indication indicating the transmission time of a downlink (DL) signal and to receive an uplink (UL) signal transmitted based on the timestamp indication.

[0032] According to a fourth aspect, an apparatus is provided. The apparatus includes one or more processors and one or more memories. The one or more memories store instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.

[0033] According to a fifth aspect, a communication system is provided. The communication system includes: a first communication device for performing the method according to the first aspect or one or more implementations of the first aspect. The communication system further includes: a second communication device for performing the method according to the second aspect or one or more implementations of the second aspect.

[0034] According to a sixth aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium stores instructions that, when executed by a device, cause the device to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect. Attached Figure Description

[0035] Figure 1 A schematic diagram of an exemplary communication system is shown;

[0036] Figure 2 Another exemplary communication system is shown;

[0037] Figure 3 An example is shown of a device communicating wirelessly with at least one of two devices in a communication system;

[0038] Figure 4 Examples of units or modules in a device or apparatus are shown;

[0039] Figure 5 An exemplary calculation process for timing advance (TA) is shown;

[0040] Figure 6 An exemplary signaling configuration indicating a timestamp of transmission time is shown;

[0041] Figure 7 An exemplary operation for estimating one-way propagation delay using timestamp indication is shown;

[0042] Figure 8 An exemplary operation is shown that uses different signals to carry timestamp indications;

[0043] Figure 9An exemplary operation of uplink (UL) timestamp indication is shown;

[0044] Figure 10 An exemplary schematic block diagram of the receiving device is shown;

[0045] Figure 11 An exemplary schematic block diagram of a transmitting device is shown. Detailed Implementation

[0046] Timing advance information for user equipment (UE) is necessary for UE uplink (UL) transmission. In some systems, timing advance (TA) information is estimated by the base station and sent to the UE as needed (e.g., when the change exceeds a minimum value such as the TA adjustment step size).

[0047] In some operations, a two-way procedure can be used to perform TA estimation. This procedure involves the UE sending a UL signal (e.g., a preamble on PRACH). The base station uses the UL transmission to estimate the TA value. The procedure also includes a DL transmission for the base station to send the TA value. The UE uses the TA value to transmit UL data services. This procedure may consume power and signaling overhead, and also introduces potential latency for the UL data.

[0048] In some implementations, a process can be implemented to provide a fast and power-efficient way to estimate the Transmission Time (TA). In one example, the base station can send a timestamp indication to the UE indicating the transmission time of a DL signal. The timestamp indication can be part of the DL signal or a different DL signal. The UE can determine the TA based on the reception time of the DL signal and the timestamp indication. In some cases, the UE can determine the TA by calculating the one-way propagation delay. The UE can then transmit a UL signal based on the determined TA. By using this process, the step of sending an initial UL signal for the base station to estimate the TA and then sending the TA to the UE can be avoided. This method reduces the latency of transmitting UL traffic. This method also reduces the wake-up time required for the UE to send the initial signal and wait for the TA, thus saving power consumption. Details of one or more implementations of the subject matter of this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages of the subject matter will become apparent from the specification, drawings, and claims.

[0049] Figure 1A schematic diagram of an exemplary communication system 100 is shown. The communication system 100 (which may be a wireless system) includes a radio access network (RAN) 120. The RAN 120 may be a next-generation (e.g., sixth-generation, 6G, or later) RAN, or a traditional (e.g., 5G, 4G, 3G, or 2nd-generation, 2G) RAN. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) may interconnect with each other or be connected to one or more network nodes (170a, 170b, collectively referred to as 170) within the RAN 120. A core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in the communication system 100. The communication system 100 may also include a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0050] Typically, communication system 100 enables multiple wireless or wired components to transmit data and other content. Communication system 100 can provide voice, data, video, and / or text content through broadcasting, multicasting, unicasting, etc. Furthermore, communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.). These services and / or applications can be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

[0051] The communication system 100 can operate by sharing resources such as carrier spectrum bandwidth among its constituent components.

[0052] Figure 2Another example of communication system 100 is shown in more detail. Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can create a heterogeneous network that can be viewed as comprising multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

[0053] Terrestrial communication systems and non-terrestrial communication systems can be subsystems of a communication system.

[0054] and Figure 1 The example shown is similar, in Figure 2In the example shown, communication system 100 may include ED 110a, 110b, 110c, 110d (collectively referred to as ED 110) and RAN 120a, 120b. Furthermore, communication system 100 may also include a non-terrestrial communication network 120c. Communication system 100 may also include one or more of a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RAN 120a, 120b include corresponding RAN nodes, such as base stations (BS) 170a, 170b, which may be collectively referred to as terrestrial transmit and receive points (T-TRP) 170a, 170b. In one implementation, the non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which can be collectively referred to as non-terrestrial transmit and receive points (NT-TRPs) 172. As can be inferred from the similarity of the reference numerals, the non-terrestrial communication network 120c can be considered a radio access network that shares operational similarities with RANs 120a and 120b. In another implementation, the non-terrestrial communication network 120c may include at least one non-terrestrial network (NTN) device and at least one corresponding terrestrial network device, wherein the at least one NTN device operates as a transport layer device, and the at least one corresponding terrestrial network device operates as a RAN node, which communicates with the ED through the NTN device. Furthermore, an NTN gateway (i.e., referred to as a terrestrial network device) may exist on the ground, which also communicates with the NTN devices as a transport layer device, and the RAN node communicates with the ED through the NTN devices and the NTN gateway. In some implementations, the NTN gateway and RAN node can be located in the same device.

[0055] Any ED 110 can be used alternatively or additionally to interface, access, or communicate with any T-TRP 170a, 170b, and NT-TRP 172, Internet 150, Core Network 130, PSTN 140, other networks 160, or any combination thereof. In some examples, ED 110a can communicate with T-TRP 170a via uplink (UL) and / or downlink (DL) transmissions through terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d can communicate with NT-TRP 172 via non-terrestrial air interface 190c for uplink and / or downlink transmissions.

[0056] Air interfaces 190a and 190b can employ similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA) (also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0057] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link (or simply a link). For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0058] RANs 120a and 120b communicate with the core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b, and / or the core network 130, can communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130, and may or may not use the same radio access technology as RANs 120a and / or RAN 120b. The core network 130 can also serve as a gateway access between (i) RANs 120a and 120b and / or EDs 110a, 110b, and 110c and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or in addition to wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels, as well as with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include computer networks and / or subnets (internal networks) and employ protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies, combined with multiple transceivers required to support these technologies.

[0059] Furthermore, the communication system 100 may include a sensing agent (not shown) to manage sensing data from ED 110 and / or T-TRP 170 and / or NT-TRP 172. In one implementation, the sensing agent is located within T-TRP 170 and / or NT-TRP 172. In another implementation, the sensing agent is a separate node with an interface for communicating with core network 130 and / or RAN 120 (e.g., T-TRP 170 and / or NT-TRP 172).

[0060] Figure 3An example is shown of a device 310 according to one embodiment wirelessly communicating with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) in a communication system (e.g., communication system 100). Device 310 may be a UE (e.g., Figure 3 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 3 The T-TRP 170 shown), and device 320b can be a non-terrestrial network device (e.g., such as...). Figure 3 (NT-TRP 172 shown). However, this is not a necessary condition. For example, according to this disclosure, device 320a can be NT-TRP, device 320b can be T-TRP, and both devices 320a and 320b can be either T-TRP or NT-TRP. In the following description, ED 110 is described as an example of device 310, T-TRP 170 is described as an example of device 320a, and NT-TRP 172 is described as an example of device 320a. Although only one device 310, one device 320a, and one device 320b are described, it should be noted that the number of devices 310 (e.g., ED 110) can be one or more, and the number of devices 320a and / or 320b can be one or more. For example, an ED 110 can be served by only one T-TRP 170 (or one NT-TRP 172), by more than one T-TRP 170, by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP 172.

[0061] The ED 110 is used to connect people, objects, and machines. It can be widely used in various scenarios, including cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), MTC, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), metaverse, digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearable devices, intelligent transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0062] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or may be referred to as, but is not limited to) the following devices: user equipment (UE) / terminal equipment, wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC equipment, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices in or including the above-mentioned equipment (e.g., communication module, modem, or chip), etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and will be referred to as T-TRP170 below. Similarly, Figure 3 As shown, the non-terrestrial (NT) device will be referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically started (i.e., established, activated, or enabled), shut down (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and / or connectivity necessity.

[0063] like Figure 3As shown, ED 110 includes at least one processor 210. Only one processor 210 is shown in the figures to avoid congestion. ED 110 may also include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figures to avoid congestion. Alternatively, one, part, or all of the antennas 204 may be panels. For example, transmitter 201 and receiver 203 may be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. ED 110 may include at least one memory 208. For simplicity, only transmitter 201, receiver 203, processor 210, memory 208 and antenna 204 are shown, but ED 110 may include one or more other components.

[0064] Memory 208 stores instructions. Memory 208 may also store data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and on-processor cache, etc.

[0065] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1 (Wired interface of Internet 150 in the network). Input / output devices or interfaces support interaction with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user and / or for communication on the network interface. For example, suitable structures include speakers, microphones, numeric keypads, keyboards, displays, touch screens, etc.

[0066] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110. As shown below and elsewhere in this disclosure, for example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), use resources for decoding one TB of the received TB, release resources for decoding another TB of the received TB, and / or receive configuration information for configuration resources. In detail, operations may include: those related to preparing to send uplink transmissions to NT-TRP 172 and / or T-TRP 170; those related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and those related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing to send uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. Processing operations related to downlink transmissions may include transmit / receive beamforming, modulation / demodulation of symbols, and encoding / decoding of symbols. According to embodiments, downlink transmissions may be received by receiver 203 (possibly using receive beamforming), and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications (e.g., beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and obtaining system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0067] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0068] The processing components of processor 210, transmitter 201, and receiver 203 may each be implemented by one or more processors, which may be the same or different, for executing instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components of processor 210, transmitter 201, and receiver 203 may each be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), graphics processing unit (GPU), or hardware accelerators such as artificial intelligence (AI) accelerators.

[0069] In some implementations, ED 110 may be a device (also referred to as a component), such as a communication module, modem, chip, or chipset, including at least one processor 210 and an interface or at least one pin. In this scenario, the transmitter 201 and receiver 203 may be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as sending information to an interface or at least one pin, or as sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin, while receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or as receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. This information may include control signaling and / or data.

[0070] like Figure 3As shown, the T-TRP 170 includes at least one processor 260. Only one processor 260 is shown in the figures to avoid congestion. The T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figures to avoid congestion. Alternatively, one, part, or all of the antennas 256 may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0071] In some implementations, the T-TRP 170 can also have other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 can be a macro base station (BS), pico BS, relay node, or host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or to a component within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0072] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) sometimes referred to as a fronthaul (e.g., a common public radio interface (CPRI)). Therefore, in some embodiments, the term "T-TRP 170" may also refer to network-side modules that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding, and are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that operate together, for example, by using coordinated multicast transmissions to serve ED 110.

[0073] The operations performed by processor 260 include those related to: preparing to transmit downlink transmissions to ED 110; processing uplink transmissions received from ED 110; preparing to transmit return transmissions to T-TRP 170 and / or NT-TRP 172; and processing transmissions received from T-TRP 170 and / or NT-TRP 172 via return. Processing operations related to preparing to transmit downlink or return transmissions may include encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via return may include receive beamforming, demodulating received symbols, and decoding received symbols. Processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 also generates an indication of beam direction (e.g., BAI), which scheduler 253 can schedule for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 can generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252.

[0074] Scheduler 253 may be coupled to or integrated into processor 260. Scheduler 253 may be included within T-TRP 170 or operate separately from it. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backlink transmissions, including issuing scheduling authorizations and / or configuring schedule-free (e.g., "configuration authorization") resources.

[0075] Memory 258 is used to store information and optionally data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, and executed by processor 260.

[0076] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0077] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may each be implemented by one or more processors, which may be the same or different, for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry (e.g., a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC).

[0078] When T-TRP 170 is a device (also referred to as a component, such as a communication module, modem, chip, or chipset in a device), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., chips, memory, or buses). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED110 can be referred to as sending information to an interface or at least one pin; and receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0079] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms including international mobile telecommunications base stations and unmanned aerial vehicles. Furthermore, in some implementations, the NT-TRP 172 may be used under other names, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0080] like Figure 3 As shown, the T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figures to avoid congestion. Alternatively, one, part, or all of the antennas 256 may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0081] like Figure 3 As shown, the NT-TRP 172 includes at least one processor 276. Only one processor 276 is shown in the figures to avoid congestion. The NT-TRP 172 may include a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figures to avoid congestion. Alternatively, one, part, or all of the antennas may be a panel. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 may also include at least one memory 278. The NT-TRP 172 may also include a scheduler 253. For simplicity, only the transmitter 272, receiver 274, processor 276, memory 278, and antenna 280 are shown, but the NT-TRP may include one or more other components.

[0082] NT-TRP 172 includes a processor 276 for performing operations related to: preparing to transmit downlink transmissions to ED 110; processing uplink transmissions received from ED 110; preparing to transmit return transmissions to T-TRP 170 and / or another NT-TRP 172; and processing transmissions received from T-TRP 170 and / or another NT-TRP 172 via return transmission. Processing operations related to preparing to transmit downlink or return transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via return transmission may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as those at the medium access control (MAC) layer or radio link control (RLC) layer. Since this is merely an example, more generally, NT-TRP 172 may implement higher-layer functions in addition to physical layer processing.

[0083] Memory 278 is used to store information and optionally data. Memory 258 stores instructions and data used, generated, or collected by NT-TRP 172. For example, memory 278 may store software instructions or modules executed by processor 276 for implementing some or all of the functions and / or embodiments described herein.

[0084] Although not shown, processor 276 may form part of transmitter 272 and / or receiver 274. Although not shown, memory 278 may form part of processor 276.

[0085] The processing components of processor 276, transmitter 272, and receiver 274 can each be implemented using one or more processors, which may be the same or different, to execute instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 can be implemented using dedicated circuitry, such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 can actually operate together to serve multiple NT-TRPs of ED 110, for example, through coordinated multicast transmissions.

[0086] When NT-TRP 172 is a device within a unit (e.g., a communication module, modem, chip, or chipset), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 272 and receiver 257 can be replaced by an interface or at least one pin, where the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as sending information to an interface or at least one pin, while receiving information from T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0087] It should be noted that the term "transmit / receive point (TRP)" as used herein can refer to either T-TRP or NT-TRP. T-TRP can be alternatively referred to as a terrestrial network TRP ("TNTRP"), and NT-TRP can be alternatively referred to as a non-terrestrial network TRP ("NTNTRP"). T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these components have been omitted for clarity.

[0088] It should be noted that, for simplicity, the term "signaling" as used herein can be alternatively referred to as control signaling, control message, control information, or message. Signaling between a BS (e.g., network node 170) and a terminal or sensing device (e.g., ED 110), or between different terminals or sensing devices (e.g., between ED 110i and ED 110j), can be carried in physical layer signaling (also known as dynamic signaling), which is transmitted in the physical layer control channel. For the downlink, physical layer signaling can be referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be referred to as uplink control information (UCI) transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., ED110i and ED 110j) can be referred to as sidelink control information (SCI) transmitted in the physical sidelink control channel (PSCCH). This signaling can be carried in higher-layer (e.g., above the physical layer) signaling, which is transmitted in the physical layer data channel. For example, for downlink signaling, it is transmitted in the physical downlink shared channel (PDSCH); for uplink signaling, it is transmitted in the physical uplink shared channel (PUSCH); and for sidelink signaling, it is transmitted in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be referred to as static signaling or semi-static signaling. Higher-layer signaling can be radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can be included in a combination of physical layer signaling and higher layer signaling.

[0089] It should be noted that in this disclosure, "information" can be carried in a single message or in more than one single message when it is different from "message".

[0090] according to Figure 4 One or more steps of the method provided in this disclosure may be performed by the corresponding unit or module. Figure 4 Examples of units or modules in devices or apparatuses such as ED 110, T-TRP 170, or NT-TRP 172 are shown. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logical, such as logical functions executed by software instructions executed by a circuit, a portion of an integrated circuit, or a processor. It should be understood that if these modules are implemented using software executed by a processor, etc., then these modules may be retrieved by the processor, in whole or in part, individually or collectively, for processing, in single or multiple instances, and these modules themselves may include instructions for further deployment and instantiation.

[0091] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0092] This disclosure pertains to devices such as UEs, IoT devices, and automobiles. The envisioned network scenarios may include terrestrial TRPs such as base stations and / or non-terrestrial TRPs such as drones, balloons, high-altitude platform stations (HAPS), satellites, and any such devices supporting wireless access technologies such as 5G NR, future 6G, or other technologies.

[0093] For illustrative purposes, specific exemplary embodiments will now be explained in more detail with reference to the accompanying drawings and the systems, EDs, and TRPs mentioned above.

[0094] The embodiments described herein illustrate information sufficient to practice the claimed subject matter and explain methods for practicing such subject matter. Those skilled in the art will understand the concepts of the claimed subject matter upon reading the following description with reference to the accompanying drawings, and will recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of this disclosure and the appended claims.

[0095] Timing advance information (TA) is used for UE uplink (UL) transmissions. The purpose of TA is to compensate for the propagation delay that occurs when a signal travels from the UE to the base station. This delay is caused by the time required for the signal to travel over the distance between the UE and the base station. In some implementations, the timing advance (TA) information can be estimated by the base station and sent to the UE as needed (e.g., if the change exceeds a minimum value such as the TA adjustment step size). To estimate the UE's TA value, a bidirectional process can be used: the UE sends at least one UL transmission based on downlink (DL) timing, and the base station can then detect this transmission and estimate the TA value. If necessary, the base station can send the TA value to the UE via downlink (DL) transmissions in control or data messages.

[0096] Figure 5 An exemplary calculation procedure 500 for timing advance (TA) is shown. In some implementations, the UE can use... Figure 5 The formula shown is based on the TA command from BS to calculate TA. Figure 5 The formula shown represents the timing advance value T. TA Based on N TA N TA,offset and T c And calculated. N TA It is calculated based on the TA command received in the random access response (also known as Msg2). N TA,offset The timing advance offset (TA) is provided by the serving cell's public information or system information. Tc is the basic time unit, calculated as follows: Tc = 1 / (480 kHz × 4096) = 0.509 ns. The TA command can be sent from the base station / serving cell to the UE based on Tc. A and / or the previous N TA Value to set N TA This adjusts the transmission timing. The value of the TA command is T. A Indicates the index value, which can be used to calculate N. TA This is to control the timing adjustment amount. In some implementations, the base station sends a TA command to the UE as needed or under certain conditions (e.g., timer timeout); the UE uses the actual timing advance value T based on the TA command. TA To adjust its transmission timing; based on T TA The adjusted timing ensures that uplink transmissions from the UE arrive at the base station at the correct or expected time.

[0097] For UE UL transmission, a TA value may be required. In some cases, the UE may remain in power-saving mode, such as inactive, idle, in sleep, or during a transmission-off cycle, and / or during mobile operation for a period of time. The UE may lose UL synchronization. Therefore, upon waking from a sleep cycle, the UE may need to obtain the appropriate TA before performing a UL transmission.

[0098] In some wireless network systems, power-saving transmissions for the network and user equipment (UE) are desirable. A fast and power-efficient transmission might be desired; for example, the UE could wake from power-saving mode during a sleep cycle configured with Discontinuous Transmission (DTX) or Discontinuous Reception (DRX), listen for and receive a low-power wake-up signal (LP-WUS) from the base station, and then perform DL reception and / or UL transmission. However, the UE may need to obtain its TA before performing any UL transmission. Therefore, for immediate UL transmissions after wake-up, TA estimation may be required, for example, before any UL transmission begins. TA estimation can be a two-way process, involving at least one UL transmission based on DL timing (whose signal is used by the base station to estimate the TA value), and a DL transmission (for the base station to send the TA value). Therefore, the process of obtaining the TA consumes more power and signaling overhead, and UL transmissions may experience more latency. This is not suitable for fast and power-efficient transmissions (i.e., immediate UL transmissions after wake-up from a sleep cycle), where TA estimation is required before any UL transmission begins.

[0099] In some implementations, a novel TA estimation procedure can be employed to estimate the UE's TA value and resolve UL synchronization issues on the UE side before UL transmission begins. This advance timing management and estimation procedure is suitable for scenarios or applications where the UE may need to resynchronize its UL synchronization or obtain a new TA for its UL transmission. Therefore, the UE may not need to first send a (special) UL signal (e.g., a preamble) to the base station so that the base station can estimate the TA value and then send the TA value to the UE during DL transmission for UL synchronization. The procedure discussed in this paper can be referred to as self-TA management and TA estimation performed by the UE itself. In this process, TA estimation is performed through a one-way transmission procedure. In one example, the UE can estimate the DL propagation delay and derive the TA based on the DL signal from the base station.

[0100] Timing advance management and estimation schemes may include one-way signal estimation on the UE side. TA can be derived at the UE side based on the one-way signal propagation delay or the difference between transmission and reception times, which can be obtained by performing one or more detections on one or more one-way (e.g., DL) transmissions.

[0101] Since the Transmission Time (TA) is used to compensate for the propagation delay of the signal from the UE to the base station, the propagation delay can be estimated through one-way signal transmission if the transmission and reception times are available. From the UE's perspective, if the DL signal is sent with a transmission timestamp, or if the UE can obtain the transmission time of the DL signal in some way, the difference between the transmission and reception times can be obtained. This difference is called the one-way propagation delay. Therefore, the UE can derive the TA estimate based on the one-way propagation delay.

[0102] Given an estimated one-way propagation delay Tprop, the timing advance value T can be estimated based on the relationship between the one-way propagation delay and other values. TA As shown below:

[0103]

[0104] Wherein: T offset It is a timing offset, which is determined by T. offset =N TA,offset Tc provides the answer. N TA,offset This is a timing advance offset for the serving cell, provided by cell group signaling or the serving cell's system information message. Tc is the basic time unit, calculated as Tc = 1 / (480 kHz × 4096) = 0.509 ns. This timing advance offset can be used to account for additional delays not covered by round-trip propagation delay. These delays can be caused by various factors, such as signal processing delays in the UE and / or base station, delays caused by the radio interface, or other factors. In some cases, this timing advance offset T... offset It can be considered as the overall calibration offset due to multiple factors, but does not include (actual) round-trip propagation delay.

[0105] Timing advance offset T offset The timing advance offset can be configured semi-statically by the network and transmitted to the UE via RRC (e.g., via an RRC reconfiguration message). The value of the timing advance offset can also depend on the frequency band, parameter set, and transmission duplex mode used in the network (e.g., full-duplex, half-duplex, time-division duplex, frequency-division duplex, etc.). Alternatively or additionally, the value of the timing advance offset can be configured in the specification protocol.

[0106] Here, TA is valued at T. TAThe estimation is based on propagation delay, which does not involve / does not require TA commands from the base station.

[0107] The UE can use the estimated TA value T above. TA To adjust its UL transmission timing in advance, for example, by T before the symbol or frame reference / boundary based on DL timing. TA Uplink transmission begins with an advance time of / 2, where DL timing is obtained based on DL synchronization using frame timing, symbol timing, or other timing. DL synchronization is determined based on one or more DL synchronization signals, which may be the same as or different from the DL signals previously discussed for one-way propagation delay estimation. Therefore, uplink transmission can arrive at the base station at the expected time.

[0108] In some implementations, the UE can detect a DL signal, the transmission timestamp of which can be carried within the DL signal or sent separately to the UE by another DL signal, thus potentially allowing the UE to obtain a one-way propagation delay. The DL signal can be a control signal or a data signal, wherein it can be higher-layer signaling (e.g., radio resource control (RRC) messages), or physical layer (e.g., L1) signaling (e.g., downlink control information (DCI)), or a data service on the PDSCH channel. In some cases, the DL signal can be a cell common service, a group common service, or a UE-specific service and / or control signal. In one example, the DL signal can be a paging message.

[0109] In some cases, a timestamp indicating the transmission time of a DL signal can be included within the DL signal itself. The transmission time can also be referred to as a transmission timestamp. In some implementations, the transmission timestamp of a DL signal can be part of the transmission information within the DL signal. For example, the transmission timestamp can be configuration signaling, indication signaling, or a separately coded block (or group of coded blocks). In some cases, the transmission timestamp can be included in the MAC CE of the DL data service, or it can be included within the DL data service itself. In some implementations, the control signaling or data service can be (e.g., via RRC) predefined or preconfigured to carry the transmission timestamp at configured times or periods using specific conditions, such as those for certain types of applications or services. In some cases, the base station can configure the type, location, periodicity, and / or other parameters of the transmission timestamp in the preconfigured control signaling or data service and send these parameters to the UE.

[0110] In some cases, the transmission timestamp of the DL signal may be provided (or included) by a second DL signal different from the DL signal. The second DL signal may be a control signal or a data service. The second DL signal may be higher-layer signaling (e.g., radio resource control (RRC) messages), or physical layer (e.g., L1) signaling (e.g., downlink control information (DCI)), or the second DL signal may be a data service on the PDSCH channel. In some cases, the second DL signal may be a cell common service, a group common service, or a UE-specific service and / or a control signal. The transmission timestamp may be part of the transmission information in the second DL signal. For example, the transmission timestamp may be configuration signaling, indication signaling, or a separately coded block (or a group of coded blocks). In some cases, the transmission timestamp may be included in the MAC CE of the DL data service, or it may be included in the DL data service itself. In other implementations, the control signaling or data service may be (e.g., via RRC) predefined or preconfigured to carry the transmission timestamp at configured time points or periods using specific conditions such as those for certain types of applications or services. In some cases, newly designed signals, a set of specially designed control signaling and / or data services can be used to carry transmission timestamps. In some cases, the base station can configure the type, location, periodicity and / or other parameters of the transmission timestamps in pre-configured control signaling or data services and send these parameters to the UE.

[0111] In operations using LP-WUS (e.g., single-transmission operations), the DL signal can be LP-WUS, LP-SS, DL service, or Level 2 DCI, where the transmission timestamp of the DL signal can be included in the DL signal. Alternatively, the transmission timestamp of the DL signal can be provided by another DL signal; for example, if the DL service is scheduled by LP-WUS, the transmission timestamp of LP-WUS can be indicated and / or included in the DL service, for example, via MAC-CE, or the transmission timestamp of LP-WUS can be indicated and / or included in Level 2 DCI. The indication of the transmission timestamp can use one or more bits, the bit length of which can depend on the time precision requirements for handling propagation (time) delays.

[0112] In some implementations, a transmission timestamp can be provided for the UL signal (e.g., UL probe signal). The transmission timestamp of the UL signal can help the base station understand the UE's timing or clock synchronization status, UE location, mobility, beam direction, etc., or achieve better timing calibration, measurement enhancement, and better sensing resolution / accuracy. In some examples, similar to the process discussed earlier regarding the transmission timestamp of the DL signal, the transmission timestamp of the UL signal can be carried within the UL signal as part of the transmitted information. Alternatively, the transmission timestamp of the UL signal can be provided (or carried) by a second UL signal different from the UL signal. The second UL signal can be a control signal or a data signal. For example, the second UL signal can be UL control information (UCI) transmitted on the PUCCH channel. For example, the second UL signal can also be a data service transmitted on the PUSCH channel. In some cases, the second UL signal can be a group common service or a UE-specific service and / or control signal.

[0113] This article provides more details on several transmission timestamp schemes.

[0114] In one example, a timestamp indication of the transmission time is provided. To estimate propagation delay based on a unidirectional (i.e., DL or UL) signal, the transmission time of the signal can be provided to the receiver, allowing the receiver to estimate the time difference between the transmission and reception times. By sending this transmission time, propagation delay estimation based on one or more unidirectional (also referred to in this disclosure as one-way, single-shot) signals can be achieved. The transmission time of the transmitted signal can be included in the transmitted signal itself (e.g., as part of data information, piggybacked, as a separately coded block or group of coded blocks, etc.) or provided in another transmitted signal (e.g., in control signaling, or piggybacked in data services), thus providing greater flexibility. How the transmission timestamp of the transmitted signal is indicated can be configured semi-statically via higher-layer signaling such as RRC, MAC-CE, and / or dynamic signaling such as DCI.

[0115] The number of bits used to indicate the transmission time of a transmitted signal can be configurable, for example, based on time accuracy / resolution requirements, application type, service type, service type, mobility, processing requirements, etc. For example, the time accuracy or resolution configuration of the transmission timestamp can be UE-specific, cell-common, or group-common. The time accuracy or resolution configuration of the transmission timestamp can also be application- or service-specific, such as Ultra-Reliable Low-Latency Communication (URLLC) or Enhanced Mobile Broadband (eMBB).

[0116] In some implementations, transmission time and other relevant parameters can be configured by the RRC information element (IE) or indicated by the DCI. Figure 6 An exemplary signaling configuration 600 is shown, indicating a timestamp representation of transmission time. For example... Figure 6 As shown, the configuration or indication includes parameters used to provide relevant information, such as timestamps like refTenNanoSeconds. Figure 6 The values ​​shown are provided as examples only. Other values ​​and / or parameters can be configured. In some implementations, the configuration or indication may include parameters for providing relevant information by including one or more of these parameters: referenceTimeInfo, referenceSFN, CellInfo, or SCS index, where referenceTimeInfo may include refMilliSeconds and / or refTenNanoSeconds.

[0117] In some implementations, a value representing the absolute time of transmission can be used to indicate the transmission time. For example, such as Figure 6 As shown, referenceTimeInfo represents absolute time using milliseconds and / or tens of nanoseconds. referenceSFN indicates the system frame number to which the configured time (or timestamp) applies. In one example, the configured timestamp can be applied to the start frame boundary. In this example, the timestamp indicates the transmission time of the start frame boundary of the frame in which the DL signal is transmitted. Figure 6It also includes other information that may be included in the timestamp indication. This information may include CellInfo and a subcarrier spacing (SCS) index. CellInfo may represent the serving cell identifier, such as the physical cell identifier, the logical cell identifier in a cell group, etc. The SCS index may be a parameter set index, such as 0, 1, 2… used to represent SCSs of 15 kHz, 30 kHz, 60 kHz, etc., respectively. The timestamp indication may include at least an indication of the transmission time (e.g., referenceTimeInfo), and one or more parameters may optionally be included. The configuration parameters and values ​​for the transmission timestamp may depend on the time estimation accuracy or resolution, such as parameter set options, application or service type, mobility, cell size, etc. For example, a transmission with a relatively small SCS (e.g., 15 kHz) may be able to use a relatively large cyclic prefix (CP), so the TA estimation (via one-way propagation delay estimation) may not (necessarily) require a relatively high time estimation resolution. In these cases, relatively coarse timestamp information can be used to indicate the transmission timestamp, meaning fewer bits are required to represent the transmission timestamp. Therefore, a subset of the integer range (0…99999) of the parameter refTenNanoSeconds can be configured and used to indicate the timestamp. In another example, a transmission with a relatively high SCS (e.g., 60 kHz) may be able to use a relatively small CP, so the TA estimation (via one-way propagation delay estimation) may require a relatively high time estimation resolution. In these cases, relatively fine-grained timestamp information can be used to indicate the transmission timestamp. Therefore, relatively more bits are needed to represent the transmission timestamp; for example, the entire integer set (0…99999) of the parameter refTenNanoSeconds can be configured and used to indicate the timestamp.

[0118] In some implementations, a value representing a relative time to a reference time can be used to indicate the transmission time. The reference time used to calculate the relative time can be an alignment point, frame boundary, subframe boundary, slot boundary, symbol boundary, or any other reference time. The alignment point is a time reference point configured by the network, specification protocol, or a combination thereof. The alignment point can be the same as or different from a frame boundary, subframe boundary, slot boundary, or symbol boundary. The reference time can be configured by the network, specification protocol, or a combination thereof. In one example, the base station can send a configuration to the UE. This configuration can configure how the relative time used for the timestamp indication is used. This configuration can indicate whether relative or absolute time is used, the reference time boundaries applied to the timestamp indication to indicate relative time, and / or the configuration of parameters in the timestamp indication, such as those discussed previously. Figure 6The configuration may include one or more information elements (IEs) in some cases. Each IE can be set to represent a value of one or more configuration parameters discussed earlier. The configuration can be transmitted using cell common services, group common services, or UE-specific services and / or control signals. The configuration can be transmitted using higher-layer signaling (e.g., radio resource control (RRC) messages), or physical layer (e.g., L1) signaling (e.g., downlink control information (DCI)), or data services.

[0119] By using relative time, fewer bits may be needed to indicate transmission time. This reduces the size of the timestamp indication and the overhead involved in sending and receiving timestamp indications. In one example, relative time can be used when DCI is used to send timestamp indications because the payload size in the DCI may be limited.

[0120] In some cases, UE timing advance (TA) management and estimation operations may include one-way signal transmission and estimation performed on the UE side. TA can be derived from the one-way signal propagation delay or the difference between the transmission time and the reception time, where propagation delay estimation can be performed using one or more one-way (e.g., DL) transmissions.

[0121] Figure 7 An exemplary operation 700 for estimating one-way propagation delay using timestamp indication is shown. Figure 7 This includes BS 702 and UE 704. UE 704 may time synchronize with BS 702 at a certain point in time (e.g., when the initial access procedure is completed, or after synchronization with DL system information (e.g., SSB) or UE-specific reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). Due to UE mobility and / or UE being in sleep mode, UL synchronization (e.g., TA used to adjust UL transmission time) may not be maintained. For example, due to UE movement, indeterminate (or unknown) propagation delays may occur. Therefore, the UE needs to resolve UL synchronization issues before performing any UL data transmission.

[0122] As described above, the TA can be derived from the one-way propagation delay based on the detection of one or more DL signals on the UE side, where a timestamp indicating the transmission time is provided for the (transmitted) DL signal. Figure 7At point 710, the DL signal is transmitted from BS 702 to UE 704. The transmission time (T_1) of the DL signal can be included in the DL signal. The DL signal can be control signaling or data service. Control signaling can be cell common control signaling, group common control signaling, or UE-specific control signaling, such as SSB, LP-WUS, low power synchronization signal (LP-SS), paging, CSI-RS, DCI, etc. Data service can include a timestamp indication in the MAC CE, as part of the information or as a separately coded block (or a group of coded blocks). The DL signal is received at point T_2.

[0123] At 720, UE 704 can determine the TA. For example, UE 704 can detect DL service and obtain the transmission time (T_1) of the DL signal based on the timestamp indication in the DL signal. Based on the transmission time (T_1) and reception time (T_2) of the DL signal, UE 704 can estimate the one-way propagation delay as T_2-T_1. UE 704 can derive the TA of the UL transmission timing based on the one-way propagation delay.

[0124] In some cases, it may be necessary to estimate the one-way propagation delay at the base station. The DL-based scheme described above can also be applied to UL, for example, by sending an uplink (UL) signal and its transmission timestamp to the base station. Figure 9 The related descriptions will provide more details on these implementations.

[0125] In some cases, a timestamp indication indicating the transmission time of a transmitted signal (e.g., a DL signal or a UL signal) may not be included in the transmitted signal. Instead, the timestamp indication of the transmission timestamp can be sent to the receiving end via another transmission signal / a separate transmission signal. For example, the transmission time of control signaling such as DCI, paging, and PDCCH can be provided (or executed) by a data service, where the data service can include the timestamp indication via MAC CE, either as part of the information or as a separately encoded block (or a group of encoded blocks).

[0126] Figure 8 An exemplary operation 800 is shown using different signals to carry timestamp indications. Figure 8This includes base station 802 and UE 804. At 810, a first DL signal is transmitted from BS 702 to UE 704. The first DL signal is transmitted at T_1 and received at T_2. The first DL signal can be control signaling or data service. Control signaling can be cell common control signaling, group common control signaling, or UE-specific control signaling, such as SSB, LP-WUS, low power synchronization signal (LP-SS), paging, CSI-RS, DCI, etc. At 820, a second DL signal is transmitted from BS 702 to UE 704. The second DL signal may include a timestamp indication (e.g., T_1) indicating the transmission of the first DL signal. The second DL signal can be control signaling or data service. Control signaling can be cell common control signaling, group common control signaling, or UE-specific control signaling, such as SSB, LP-WUS, low power synchronization signal (LP-SS), paging, CSI-RS, DCI, etc. Data services can include timestamp indications in MAC CE, either as part of the message or as a separate encoded block (or a group of encoded blocks).

[0127] For the UE, in order to obtain the appropriate TA using the proposed one-way propagation delay estimate, the UE can perform the following procedure (where the transmission timestamp of the DL service is provided to the UE):

[0128] • Detect DL service and obtain Tx time T_1;

[0129] • Estimate the one-way propagation delay, where T prop =T_2-T_1, where T_2 is the reception time of the DL service;

[0130] • Derive the TA value T for UL transmission timing using the following formula. TA

[0131]

[0132] Wherein, parameter T offset N TA,offset Tc is defined as previously described in this disclosure.

[0133] Figure 9 An exemplary operation 900 of UL timestamp indication is shown. Figure 9This includes BS 902 and UE 904. At 910, the UL signal is transmitted from UE 904 to BS 902. At 920, BS 902 estimates the TA based on the transmission timestamp and reception time T_4 included in the UL signal. For the BS, in order to obtain the appropriate TA using the proposed one-way propagation delay estimate, BS 902 can perform the following procedure (where the transmission timestamp of the UL service is provided to the BS):

[0134] • Inspect UL services and obtain Tx time T_3;

[0135] • Estimate the one-way propagation delay, where T prop =T_4-T_3, where T_4 is the reception time of the UL service;

[0136] • The TA value T of UL is derived for UL transmission timing using the following formula. TA

[0137]

[0138] like Figure 9 As shown, BS 902 can use unidirectional transmission to estimate (UL) propagation delay, where a timestamp indication of the transmission time of the UL service can be included in the UL service. Alternatively, the timestamp indication can be provided by another UL service or control signal. Therefore, BS 902 can obtain the propagation delay between UE 904 and BS 902. Thus, BS 902 can determine UL channel characteristics, such as UE location, UL path loss, UL coverage, etc. BS 902 can perform associated actions (e.g., timing calibration with the UE and / or enhanced scheduling) to improve measurement accuracy / resolution, communication or sensing efficiency, etc.

[0139] Exemplary operations for TA estimation discussed in this disclosure may include:

[0140] Step 1: The base station sends information indicating one or more configuration parameters discussed earlier. The UE receives this information accordingly.

[0141] This information can be carried via RRC / MAC / DCI signaling or any combination thereof. Alternatively, this information can also be carried via data services.

[0142] This step is optional, and if omitted, one or more of the configuration parameters mentioned above can be predefined. For example, configuration parameters can be associated with specific applications or services.

[0143] Step 2: The UE applies one or more configured parameters to continue performing TA estimation and / or TA management.

[0144] Step 3: The base station performs DL transmission to the UE.

[0145] In some cases, a timestamp indicating the transmission time (T_1) of a DL transmission is carried within the DL transmission itself. Alternatively or additionally, a timestamp indicating the transmission time of a DL transmission is carried within a separate DL transmission.

[0146] The base station is not required to carry a timestamp indication in every DL transmission. Instead, the base station can carry a timestamp indication when needed. For example, the UL arrival time of a UL transmission may not be the expected arrival time.

[0147] The UE estimates the TA based on the received DL transmission time and the timestamp indicating the transmission time of the DL transmission.

[0148] Step 4: The UE uses the estimated TA to perform UL transmission.

[0149] Exemplary operations for TA estimation discussed in this disclosure may include:

[0150] Step 1: The base station sends information indicating one or more configuration parameters discussed earlier. The UE receives this information accordingly.

[0151] This information can be carried via RRC / MAC / DCI signaling or any combination thereof. Alternatively, this information can also be carried via data services.

[0152] This step is optional, and if omitted, one or more of the configuration parameters mentioned above can be predefined. For example, configuration parameters can be associated with specific applications or services.

[0153] Step 2: The UE uses configuration parameters to perform UL transmission to the base station.

[0154] In some cases, a timestamp indicating the transmission time (T_3) of a UL transmission is carried within the UL transmission itself. Additionally, a timestamp indicating the transmission time of a UL transmission may be carried within a different UL transmission.

[0155] Step 3: The base station obtains the propagation delay.

[0156] Base stations may apply propagation delay for various purposes. For example, a base station may estimate the location of a UE based on the obtained propagation delay, and / or improve scheduling by adjusting the modulation and coding scheme (MCS) used for data transmission and / or the aggregation level (AL) used for PDCCH transmission.

[0157] Optionally, the base station performs TA estimation and / or TA management based on information carried in the UL transmission (e.g., T_3).

[0158] Step 4: The base station indicates the estimated TA to the UE.

[0159] This step is optional.

[0160] Figure 10 An exemplary schematic block diagram of a receiving device 1000 is shown. The receiving device 1000 can be implemented as an apparatus for receiving an operational timestamp indication as discussed in this disclosure. Figure 10 As shown, the receiving device 1000 includes:

[0161] The receiving module 1010 is used to receive a timestamp indication indicating the transmission time of the downlink (DL) signal;

[0162] The determination module 1020 is used to determine the timing advance (TA) based on the reception time and timestamp indication of the DL signal.

[0163] The transmitting module 1030 is used to transmit an uplink (UL) signal according to the determined TA.

[0164] The aforementioned management operations and / or functions, as well as other management operations and / or functions, of the modules of the receiving device 1000 are intended to implement the corresponding steps of the above method. For the sake of brevity, details are not elaborated herein.

[0165] The receiving module 1010 and the transmitting module 1030 can be implemented by transceivers, or by receivers or transmitters, respectively. The determining module 1020 can be implemented by one or more processors.

[0166] Figure 11 An exemplary schematic block diagram of a transmitting device 1100 is shown. The transmitting device 1100 can be implemented as a means of transmitting a timestamp indication according to the operation discussed in this disclosure. Figure 11 As shown, the transmitting device 1100 includes:

[0167] The transmitting module 1110 is used to transmit a timestamp indication indicating the transmission time of the downlink (DL) signal.

[0168] The receiving module 1120 is used to receive uplink (UL) signals transmitted based on timestamp indications.

[0169] The aforementioned management operations and / or functions, as well as other management operations and / or functions, of the modules of the transmitting device 1100 are intended to implement the corresponding steps of the above-described method. For the sake of brevity, details are not elaborated herein.

[0170] The receiving module 1120 and the transmitting module 1110 can be implemented by transceivers, or by receivers or transmitters, respectively.

[0171] In some aspects of this disclosure, an apparatus / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE of this disclosure (or implemented at a UE of this disclosure). The apparatus / chipset system may be a UE (i.e., a terminal device) or a module / component within a UE. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0172] In some aspects of this disclosure, an apparatus / chipset system is provided, including components (e.g., at least one processor) for implementing methods implemented by a network device (e.g., a base station) of this disclosure (or at a network device (e.g., a base station) of this disclosure). The apparatus / chipset system may be a network device or a module / component within a network device. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method. In some aspects of this disclosure, a system is provided, including at least one device in a UE (or at a UE) of this disclosure or in a network device of this disclosure (or at a network device of this disclosure).

[0173] In some aspects of this disclosure, a method is provided performed by a system comprising at least one of means in (or at the UE of this disclosure) a UE of this disclosure and means in (or at the network device of this disclosure).

[0174] In some aspects of this disclosure, a computer program comprising instructions is provided. When executed by a processor, the instructions enable the processor to implement the methods of this disclosure.

[0175] In some aspects of this disclosure, a non-transitory computer-readable medium is provided that stores instructions that, when executed by a processor, enable the processor to implement the methods of this disclosure.

[0176] The schemes described in this disclosure are applicable to next-generation (e.g., sixth-generation, 6G or higher) networks, or traditional (e.g., 5G, 4G, 3G or 2G) networks.

[0177] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing information, such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes: magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices; compact disc read-only memory (CD-ROM), digital video disc or digital versatile disc (i.e., DVD), Blu-ray disc™, or other optical storage devices; volatile and non-volatile, removable and non-removable media implemented using any method or technology; random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other storage technologies. Any such non-transitory computer / processor storage medium may be part of a device or apparatus, or may be accessible or connected to by a device or apparatus. Computer / processor-readable / executable instructions used to implement the methods, applications, or modules described herein may be stored by such non-transitory computer / processor-readable storage media or otherwise preserved.

[0178] It should be noted that the term "message" in this disclosure can be replaced with "information," which may be contained in a single message or in more than one separate message.

[0179] Unless otherwise specified, the terms “apparatus” and “equipment” are used interchangeably, as are the terms “identifier” and “identifier”.

[0180] In this disclosure, when used in conjunction with the term "comprising" in the claims and / or specification, the word "a" or "an" may mean "one," but it also has the same meaning as "one or more," "at least one," and "one or more," unless explicitly stated otherwise. Similarly, the word "another" may refer to at least a second or more, unless explicitly stated otherwise.

[0181] In this disclosure, when used before the same term (e.g., ED or operational step), the words “first,” “second,” etc., do not imply an order or sequence of the terms. For example, without specific indication, “first ED” and “second ED” mean two different EDs; similarly, without specific indication, “first step” and “second step” mean two different operational steps, but this does not mean that the first step must occur before the second step. The actual order depends on the logic of the two steps.

[0182] The terms “coupling” or “connection” as used herein can have several different meanings depending on the context in which they are used. For example, depending on the specific context, “coupling” or “connection” as used herein can mean two elements or devices that are directly connected to each other or that are connected to each other by mechanical elements through one or more intermediate elements or devices.

[0183] It should be noted that the expression "at least one of A or B" as used herein is interchangeable with the expression "A and / or B". This expression refers to a list in which A or B, or both A and B, can be selected. Similarly, the expression "at least one of A, B, or C" as used herein is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This expression refers to a list in which: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B, and C can be selected. The same principle applies to longer lists with the same format.

[0184] This disclosure covers a variety of embodiments, including not only method embodiments but also other embodiments, such as apparatus embodiments and embodiments related to non-transitory computer-readable storage media. Embodiments may be incorporated individually or in combination with the features disclosed herein.

[0185] The terms “receive,” “detect,” and “decode” as used herein can have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” can indicate that information (e.g., DCI or MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can include both “detect” and “decode,” or it can indicate the same thing; for example, “receive paging” means that the paging was correctly decoded and successfully obtained, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. “Not received paging” means that the receiving side attempted to detect and / or decode the paging but was unsuccessful in obtaining the paging. The term “receive” can sometimes indicate that a signal has arrived at the receiving side, but does not imply that the information in the signal has been correctly detected and decoded. The receiving side needs to perform detection and decoding on the signal to obtain the information carried in the signal. In this scenario, “receive,” “detect,” and “decode” can indicate different processes by which the receiving side obtains the information. In this disclosure, the terms “send” and “transmit” are used interchangeably in the embodiments of this application.

[0186] While this disclosure refers to illustrative embodiments, it is not intended to be construed as limiting. Those skilled in the art will recognize various modifications and combinations of the illustrative embodiments, as well as other embodiments of this disclosure, upon referring to this description. When two or more embodiments are combined, not all features in the embodiments to be combined are necessary for the combination.

[0187] Features disclosed herein in the context of any particular embodiment may be implemented additionally or alternatively in other embodiments. For example, method embodiments may be implemented additionally or alternatively in apparatus, system, and / or computer program product embodiments. Additionally, although embodiments are described primarily in the context of methods and apparatus, other implementations are contemplated as instructions stored in one or more non-transitory computer-readable media, etc. Such media may store programs or instructions to perform any of the various methods consistent with this disclosure.

Claims

1. A method, characterized in that, include: Receive a timestamp indicating the transmission time of the downlink (DL) signal; The timing advance (TA) is determined based on the reception time of the DL signal and the timestamp indication. The uplink (UL) signal is sent based on the determined TA.

2. The method according to claim 1, characterized in that, The DL signal includes cell common control signaling, group common control signaling, or user equipment (UE) specific control signaling.

3. The method according to claim 1 or 2, characterized in that, The DL signaling includes paging messages.

4. The method according to any one of claims 1 to 3, characterized in that, The DL signal includes DL data services.

5. The method according to any one of claims 1 to 4, characterized in that, The timestamp indication is included in the DL signal.

6. The method according to any one of claims 1 to 5, characterized in that, The timestamp indication is included in another DL signal that is different from the DL signal.

7. The method according to any one of claims 1 to 6, characterized in that, The timestamp indication includes an absolute time value.

8. The method according to any one of claims 1 to 7, characterized in that, The timestamp indication includes a relative time value.

9. The method according to any one of claims 1 to 8, characterized in that, Also includes: The configuration for receiving the timestamp indication includes an indication of a reference time boundary applied to the timestamp indication.

10. The method according to any one of claims 1 to 9, characterized in that, Determining the TA based on the reception time of the DL signal and the timestamp indication includes: The one-way propagation delay is determined based on the reception time of the DL signal and the timestamp indication; The TA is determined based on the one-way propagation delay.

11. The method according to any one of claims 1 to 10, characterized in that, The TA is also determined based on the timing offset.

12. The method according to any one of claims 1 to 11, characterized in that, Also includes: Send a second timestamp indicating the transmission time of the UL signal.

13. A method, characterized in that, include: Sends a timestamp indicating the transmission time of the downlink (DL) signal; Receive uplink (UL) signals transmitted based on the timestamp indication.

14. The method according to claim 13, characterized in that, The DL signal includes cell common control signaling, group common control signaling, or user equipment (UE) specific control signaling.

15. The method according to claim 13 or 14, characterized in that, The DL signaling includes paging messages.

16. The method according to any one of claims 13 to 15, characterized in that, The DL signal includes DL data services.

17. The method according to any one of claims 13 to 16, characterized in that, The timestamp indication is included in the DL signal.

18. The method according to any one of claims 13 to 17, characterized in that, The timestamp indication is included in another DL signal that is different from the DL signal.

19. The method according to any one of claims 13 to 18, characterized in that, The timestamp indication includes an absolute time value.

20. The method according to any one of claims 13 to 19, characterized in that, The timestamp indication includes a relative time value.

21. The method according to any one of claims 13 to 20, characterized in that, Also includes: The configuration for sending the timestamp indication includes an indication of a reference time boundary applied to the timestamp indication.

22. The method according to any one of claims 13 to 21, characterized in that, Also includes: Receive a second timestamp indicating the transmission time of the UL signal.

23. A communication device, characterized in that, Used to perform the method according to any one of claims 1 to 22.

24. The communication device according to claim 23, characterized in that, include: The receiving unit is used to receive a timestamp indicating the transmission time of the downlink (DL) signal; The determining unit is used to determine the timing advance (TA) based on the reception time of the DL signal and the timestamp indication. The transmitting unit is used to transmit uplink (UL) signals according to the determined TA.

25. The communication device according to claim 23, characterized in that, include: The transmitting unit is used to transmit a timestamp indication indicating the transmission time of the downlink (DL) signal; A receiving unit is configured to receive an uplink (UL) signal transmitted based on the timestamp indication.

26. The communication device according to claim 23, characterized in that, include: Interface circuitry for receiving a timestamp indicating the transmission time of a downlink (DL) signal; One or more processors are configured to determine a timing advance (TA) based on the reception time of the DL signal and the timestamp indication. The interface circuit described therein is used to send an uplink (UL) signal according to the determined TA.

27. The communication device according to claim 23, characterized in that, include: One or more processors; Interface circuit, used for: Sends a timestamp indicating the transmission time of the downlink (DL) signal; Receive uplink (UL) signals transmitted based on the timestamp indication.

28. The communication device according to claim 26 or 27, characterized in that, The interface circuit includes one or more transceivers.

29. An apparatus, characterized in that, include: One or more processors; One or more memories, the one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of claims 1 to 22.

30. A communication system, characterized in that, The communication system includes: a first communication device for performing the method according to any one of claims 1 to 12; and a second communication device for performing the method according to any one of claims 13 to 22.

31. A non-transitory computer-readable storage medium, characterized in that, It stores instructions that, when executed by the device, cause the device to perform the method according to any one of claims 1 to 22.

Images