Method and apparatus for rx-tx time difference reporting

Abstract

The present disclosure relates to methods and devices, including apparatuses, e.g., UEs and / or base stations, for wireless communication. In one aspect, an apparatus can receive, from a base station via RRC signaling, an SPS. The apparatus can also determine a UE Rx-Tx time difference, the UE Rx-Tx time difference being equal to a difference between a downlink subframe reception time and an uplink subframe transmission time. The apparatus can also transmit, to the base station, the UE Rx-Tx time difference or receive, from the base station, a base station Rx-Tx time difference, the base station Rx-Tx time difference being equal to a difference between an uplink subframe reception time and a downlink subframe transmission time.

Description

Technical Field

[0001] In summary, this disclosure relates to communication systems, and more specifically, to time difference reporting in wireless communication systems. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA).

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0004] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may receive semi-persistent scheduling (SPS) from a base station via radio resource control (RRC) signaling. The apparatus may also determine the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. The apparatus may also monitor the physical downlink control channel (PDCCH) from the base station and receive the PDCCH from the base station, wherein the PDCCH indicates whether to transmit the UE Rx-Tx time difference or receive the base station Rx-Tx time difference. Additionally, the apparatus may determine whether at least one uplink resource is available for transmission. The apparatus may also transmit the UE Rx-Tx time difference to the base station or receive the base station Rx-Tx time difference from the base station, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. Furthermore, when receiving the base station Rx-Tx time difference from the base station, the device can calculate the propagation delay value, where the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference. Additionally, when sending the UE Rx-Tx time difference to the base station, the device can receive the propagation delay value from the base station, where the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference.

[0006] In another aspect of this disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a base station. The apparatus may transmit semi-persistent scheduling (SPS) to a user equipment (UE) via Radio Resource Control (RRC) signaling. The apparatus may also determine a base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. The apparatus may also transmit a Physical Downlink Control Channel (PDCCH) to the UE, wherein the PDCCH indicates whether to transmit the base station Rx-Tx time difference or receive the UE Rx-Tx time difference. Furthermore, the apparatus may transmit the base station Rx-Tx time difference to the UE or receive the UE Rx-Tx time difference from the UE, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. When transmitting the base station Rx-Tx time difference to the UE, the apparatus may receive a propagation delay value from the UE, where the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference. When receiving the UE Rx-Tx time difference from the UE, the device can calculate the propagation delay value, where the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference.

[0007] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which they can be implemented according to the principles of each aspect, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0010] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0011] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0012] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0013] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0014] Figure 4 This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0015] Figure 5A and 5B This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0016] Figure 6A and 6B This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0017] Figure 7A and 7B This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0018] Figure 8 This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0019] Figure 9This is a diagram illustrating example communication between a UE and a base station using one or more technologies according to this disclosure.

[0020] Figure 10 This is a flowchart of a wireless communication method.

[0021] Figure 11 This is a flowchart of a wireless communication method.

[0022] Figure 12 This is a diagram illustrating an example of how the hardware implementation of the example device is used.

[0023] Figure 13 This is a diagram illustrating an example of how the hardware implementation of the example device is used. Detailed Implementation

[0024] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. Specific details are included in the specific embodiments for the purpose of providing a full understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0025] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0026] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described herein. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0027] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code accessible by a computer in the form of instructions or data structures.

[0028] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0029] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0030] Base station 102 can wirelessly communicate with UE 104. Each base station 102 in the base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB), which can provide services to restricted groups referred to as Closed Subscriber Groups (CSGs). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0031] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0032] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0033] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as that used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0034] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "below 6GHz" band. Similar naming issues sometimes arise regarding FR2; although different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0035] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "below 6 GHz" and the like (if used herein) can broadly refer to frequencies that are less than 6 GHz, frequencies that are within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies that may include intermediate frequency bands, frequencies that are within FR2, or frequencies that are within the EHF band.

[0036] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0037] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0038] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for MBMS transmissions to content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to areas of Multicast-Broadcast Single Frequency Networks (MBSFNs) that broadcast specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0039] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming service, and / or other IP services.

[0040] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0041] Refer again Figure 1In some aspects, UE 104 may include a receiving component 198 configured to receive semi-persistent scheduling (SPS) from a base station via radio resource control (RRC) signaling. The receiving component 198 may also be configured to determine the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. The receiving component 198 may also be configured to monitor the physical downlink control channel (PDCCH) from the base station and to receive the PDCCH from the base station, wherein the PDCCH indicates whether to transmit the UE Rx-Tx time difference or receive the base station Rx-Tx time difference. The receiving component 198 may also be configured to determine whether at least one uplink resource is available for transmission. The receiving component 198 may also be configured to transmit the UE Rx-Tx time difference to the base station or receive the base station Rx-Tx time difference from the base station, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. Furthermore, when receiving the base station Rx-Tx time difference from the base station, the receiving component 198 can also be configured to calculate a propagation delay value, wherein the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference. Furthermore, when transmitting the UE Rx-Tx time difference to the base station, the receiving component 198 can be configured to receive a propagation delay value from the base station, wherein the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference.

[0042] Refer again Figure 1In some aspects, base station 180 may include transmission component 199 configured to transmit semi-persistent scheduling (SPS) to user equipment (UE) via radio resource control (RRC) signaling. Transmission component 199 may also be configured to determine the base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. Transmission component 199 may also be configured to transmit a physical downlink control channel (PDCCH) to the UE, wherein the PDCCH indicates whether to transmit the base station Rx-Tx time difference or receive the UE Rx-Tx time difference. Transmission component 199 may also be configured to transmit the base station Rx-Tx time difference to the UE or receive the UE Rx-Tx time difference from the UE, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. When transmitting the base station Rx-Tx time difference to the UE, the transmission component 199 can also be configured to receive a propagation delay value from the UE, wherein the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference. When receiving the UE Rx-Tx time difference from the UE, the transmission component 199 can also be configured to calculate a propagation delay value, wherein the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference.

[0043] Although the following description may focus on 5G NR, the concepts described herein can be applied to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0044] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G NR frame structure. Figure 2B This is a schematic diagram 230 showing an example of a DL channel within a 5G NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D This is a schematic diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL), or Time Division Duplex (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL). In the process of... Figure 2A , 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the TDD 5G NR frame structure.

[0045] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2DExamples are provided for slot configuration 0 (14 symbols per slot) and digital scheme μ=2 (4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing can exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme.

[0046] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which consists of 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0047] As in Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration). x However, other DM-RS configurations are possible) and Channel State Information Reference Signal (CSI-RS). RS can also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0048] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0049] As in Figure 2C As shown, some of the REs in the diagram carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols preceding the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0050] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and may also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0051] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0052] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0053] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359 for layer 3 and layer 2 functions.

[0054] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0055] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0056] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0057] UL transmission at base station 310 is handled in a manner similar to that described for the receiver functions integrated at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0058] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0059] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 All aspects related to 198.

[0060] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 All aspects related to 199.

[0061] Some aspects of wireless communication include numerous enhancements, such as physical (PHY) layer feedback enhancements for meeting Ultra-Reliable Low-Latency Communication (URLLC), UE feedback enhancements, and / or CSI feedback enhancements to allow for more accurate modulation and coding scheme (MCS) selection. Wireless communication may also include uplink enhancements for URLLC in unlicensed controlled environments. Aspects of wireless communication may also include UE-initiated Channel Occupancy Time (COT) for Frame-Based Equipment (FBE). Additionally, wireless communication may include permission enhancements that coordinate uplink configurations in URLLC, which are introduced to suit unlicensed spectrum.

[0062] In some aspects of wireless communication, there may be intra-UE multiplexing and priority ordering of services with different priorities. Various aspects of wireless communication can also specify multiplexing behavior between HARQ-ACK, SR, or CSI and PUSCH for services with different priorities, including the case of UCI on PUCCH and UCI on PUSCH. Various aspects of wireless communication can also specify overlapping dynamically allowed PUSCHs with different PHY priorities on the serving cell's bandwidth portion (BWP) and the configured PHY priority ordering of allowed PUSCHs, including related cancellation behavior for PUSCHs with lower PHY priorities.

[0063] Some aspects of wireless communication may also include enhancements to support time synchronization. For example, for Time-Sensitive Networks (TSNs), there may be uplink time synchronization. There may also be propagation delay compensation enhancements, including for mobility issues. Additionally, there may be enhancements based on Quality of Service (QoS) related parameters such as time to lifetime and burst spread.

[0064] In some aspects, if the TSN master clock is at the terminal station connected to the first UE (UE1) and can be relayed to the terminal station connected to the second UE (UE2), the two Uu interfaces may introduce uncertainties exceeding the maximum allowed uncertainty for the wireless communication system (e.g., 900 ns). For the radio link, the propagation delay can be half of the timing advance (TA). Alternative methods may also exist for determining the downlink propagation delay value used to adjust the 5G reference time. For example, there may be a conventional timing advance procedure that can be used to determine the downlink propagation delay. This conventional procedure can help determine which corresponding sources of uncertainty can be mitigated to meet the synchronization specifications of each Uu interface. Furthermore, there may be a procedure for timing advance calculation based on time difference measurements, which can be based on two measurements: the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference and the base station Rx-Tx time difference.

[0065] Figure 4 Figure 400 illustrates an example communication between UE 402 and base station 404. (See Figure 400.) Figure 4 As shown in Figure 400, t 411 and t 412 , t 411 It is the uplink transmission time of frame 420 at UE 402, t 412 This is the uplink reception time of frame 410 at base station 404. Figure 400 also includes t. 413 and t 414 , t 413 It is the downlink transmission time of frame 421 at base station 404, t 414 This is the downlink reception time of frame 421 at UE 402. Additionally, Figure 400 includes the UE Rx-Tx time difference (UE Rx-Tx time difference). Rx-Tx (e.g., t) 411 -t 414 ) and base station Rx-Tx time difference (gNB) Rx-Tx (For example, t) 412 -t 413 ).

[0066] Figure 4 The procedure for allowing a UE to determine the value of the downlink propagation delay is illustrated, which can utilize the enhanced round-trip time (RTT) method. For example... Figure 4 As shown, some aspects of wireless communication can utilize multiple definitions for propagation delay. For example, the UE Rx-Tx time difference can be defined as t4–t1. For instance, t4 could be the UE reception timing of the downlink subframe (e.g., subframe i) defined by the path detected first in time. Furthermore, t1 could be the UE transmission timing of the uplink subframe (e.g., subframe j) that is closest in time to subframe i. Figure 4 As shown, the base station Rx-Tx time difference can be defined as t3–t2. Furthermore, t3 can be the base station reception timing of the uplink subframe (e.g., subframe i) containing the appropriate SRS associated with the UE, which can be defined by the path detected first in time. Additionally, t2 can be the base station transmission timing of the downlink subframe (e.g., subframe j) that is closest in time to the subframe i received from the UE.

[0067] Figure 5A and 5B Figures 500 and 550 show example communications between UE 502 / 552 and base station 504 / 554, respectively. Figure 5A and 5B This illustrates two possibilities regarding how signaling occurs between the UE and the base station, so that RTT information for delay compensation can be successfully obtained at the UE.

[0068] like Figure 5A As shown in Figure 500, t 511 and t 512 , t 511 It is the uplink transmission time of frame 520 at UE 502, t 512 This is the uplink reception time of frame 520 at base station 504. Figure 500 also includes t. 513 and t 514 , t 513 It is the downlink transmission time of frame 521 at base station 504, t 514 This is the downlink reception time of frame 521 at UE 502. Additionally, Figure 500 includes the UE Rx-Tx time difference (UE Rx-Tx time difference). Rx-Tx (For example, t) 511 -t 514 ) and base station Rx-Tx time difference (gNB) Rx-Tx (For example, t) 512 -t 513 ). Figure 5A This illustrates a one-step exchange for obtaining round-trip time (RTT) information. For example, base station 504 can directly send the base station Rx-Tx time difference (gNB) to UE 502 using signals. Rx-Tx The value of ) can then be used by UE 502 to calculate the UE Rx-Tx time difference (UE Rx-Tx time difference).Rx-Tx The time difference between the UE and the base station Rx-Tx is added together (e.g., UE Rx-Tx time difference). Rx-Tx +gNB Rx-Tx This can be used to directly calculate the RTT or propagation delay value.

[0069] like Figure 5B As shown in Figure 550, t 561 and t 562 , t 561 It is the uplink transmission time of frame 570 at UE 552, t 562 This refers to the uplink reception time of frame 570 at base station 554. Figure 550 also includes t. 563 and t 564 , t 563 It is the downlink transmission time of frame 571 at base station 554, t 564 This is the downlink reception time of frame 571 at UE 552. Additionally, Figure 550 includes the UE Rx-Tx time difference (UE Rx-Tx time difference). Rx-Tx (For example, t) 561 -t 564 ) and base station Rx-Tx time difference (gNB) Rx-Tx (For example, t) 562 -t 563 ). Figure 5B This illustrates a two-step exchange for obtaining RTT information. For example, UE 552 can send a signal to base station 554. Rx-Tx Value. Base station 554 can add the values ​​of the time difference (e.g., UE). Rx-Tx +gNB Rx-Tx The base station 554 can then calculate the RTT or propagation delay value. The base station 554 can then directly send the propagation delay value for compensation to the UE 552 via a signal.

[0070] As mentioned above, RTT can be introduced for positioning. If RTT is used for propagation delay compensation, there are two possibilities for signaling between the UE and the base station. However, it may be uncertain when signaling between the UE and the base station will be triggered. Based on the above, it may be beneficial to also consider when signaling between the UE and the base station will be triggered. For example, it may be beneficial to determine when either the Rx-Tx time difference is triggered or transmitted. Accordingly, it may be beneficial to determine when the UE Rx-Tx time difference and the base station Rx-Tx time difference are transmitted or received.

[0071] Various aspects of this disclosure may consider when to trigger signaling between the UE and the base station. For example, various aspects of this disclosure may determine when to trigger or transmit any of the Rx-Tx time differences. Therefore, various aspects of this disclosure may determine when to transmit or receive the UE Rx-Tx time difference and the base station Rx-Tx time difference. Various aspects of this disclosure may consider multiple options for triggering the Rx-Tx time difference, such as periodically transmitting or receiving the Rx-Tx time difference. Furthermore, this disclosure may trigger Rx-Tx time difference transmission based on a specific event.

[0072] In some aspects, the periodic transmission of the Rx-Tx time difference can include different scenarios or transmission sequences. In one aspect, the base station can send the base station Rx-Tx time difference (gNB Rx-Tx) to the UE. In this aspect, the base station can use SPS PDSCH to send the Rx-Tx time difference to the UE. In another aspect, the UE can send the UE Rx-Tx time difference (UERx-Tx) to the base station. In this aspect, the UE can use uplink configuration permission (CG) to send the UE Rx-Tx time difference to the base station.

[0073] Furthermore, various aspects of this disclosure may include multiple options for scheduling or transmission of a configuration activating the Rx-Tx time difference. In one aspect, Radio Resource Control (RRC) signaling may automatically activate the scheduling or transmission of a configuration activating the Rx-Tx time difference. In another aspect, PDCCH may be used to activate the scheduling or transmission of a configuration activating the Rx-Tx time difference.

[0074] Figure 6A and 6B Figures 600 and 650 show example communications between UE 602 / 652 and base station 604 / 654, respectively. Figure 6A and 6B This shows the time difference (gNB) between base station 604 / 654 and UE 602 / 652 when base station sends Rx-Tx data. Rx-Tx ).like Figure 6A As shown in Figure 600, UE 602, base station 604, SPS 610 and base station Rx-Tx time difference 620 / 621 / 622 are included. Figure 6A Transmissions depicting the Rx-Tx time difference 620 / 621 / 622 at base stations can be activated via SPS 610 through RRC signaling. For example... Figure 6B As shown in Figure 650, UE 652, base station 654, SPS 660, UE monitoring PDCCH 662, PDCCH 664 and base station Rx-Tx time difference 670 / 671 / 672 are included. Figure 6BThe transmission of base station Rx-Tx time difference 670 / 671 / 672 can be activated by PDCCH 664 from base station 654.

[0075] Figure 7A and 7B Figures 700 and 750 show example communications between UE 702 / 752 and base station 704 / 754, respectively. Figure 7A and 7B This displays the time difference (UE Rx-Tx) sent by UE 702 / 752 to base station 704 / 754. Rx-Tx ).like Figure 7A As shown in Figure 700, UE 702, base station 704, SPS 710, and UE Rx-Tx time difference 720 / 721 / 722 are included. Figure 7A Transmissions depicting the UE Rx-Tx time difference 720 / 721 / 722 can be activated via SPS 710 through RRC signaling. For example... Figure 7B As shown in Figure 750, UE 752, base station 754, SPS 760, UE monitoring PDCCH 762, PDCCH 764, and UE Rx-Tx time difference 770 / 771 / 772 are included. Figure 7B The transmission of UE Rx-Tx time difference 770 / 771 / 772 can be activated by PDCCH 764 from base station 754.

[0076] As indicated herein, periodic Rx-Tx time difference measurements and signaling or transmissions can be handled via RRC signaling. Aspects of this disclosure can also map Rx-Tx time difference messages (e.g., MAC CE or RRC messages) to configured permissioned (CG) instances. For example, when a base station sends a base station Rx-Tx time difference (gNB Rx-Tx) to a UE, the base station can schedule an SPS PDSCH. When a UE sends a UE Rx-Tx time difference (UE Rx-Tx) to a base station, aspects of this disclosure can utilize a predefined time offset between the physical (PHY) layer and the RRC message or MAC-CE. This time offset allows RRC to complete the measurement and signaling, and then the Rx-Tx time difference message can be generated in a timely manner for the current CG timing.

[0077] In some instances, when the UE sends the UE Rx-Tx time difference to the base station, aspects of this disclosure can disable scheduling requests (SRs) at a more granular level. For example, a certain SR that is disabled at the logical channel level can disable SRs for all RRC messages, but this disabling may not be available for MAC CE. This could lead to delays in more important RRC messages, such as measurement report messages used for handover. To address this issue, aspects of this disclosure can disable SRs at a more granular level. For example, this disclosure can disable SRs for RRC message groups or MAC CE groups.

[0078] Additionally, when the UE sends the UE Rx-Tx time difference to the base station, various aspects of this disclosure may introduce an SR delay timer. To avoid delaying more important RRC messages (such as measurement report messages used for handover), this disclosure may introduce an SR delay timer for specific RRC message groups or MAC CE groups. Furthermore, when the UE sends the UE Rx-Tx time difference to the base station, various aspects of this disclosure may define a new logical channel for a specific RRC message group. Various aspects of this disclosure may disable SR or introduce an SR delay timer for logical channels.

[0079] In some aspects, periodic transmission of the Rx-Tx time difference can lead to resource consumption because the Rx-Tx time difference may vary slightly over a long period. Various aspects of this disclosure can utilize resources more efficiently. For example, this disclosure can consider non-periodic transmission of the Rx-Tx time difference. Furthermore, Rx-Tx time difference transmission can be triggered based on some specified event.

[0080] Figure 8 Figure 800 illustrates an example communication between UE 802 and base station 804. (See Figure 800.) Figure 8 As shown in Figure 800, t 811 and t 812 , t 811 It is the uplink transmission time of frame 820 at UE 802, t 812 This is the uplink reception time of frame 820 at base station 804. Figure 800 also includes t. 813 And t814, t 813 It is the downlink transmission time of frame 821 at base station 804, t 814 This is the downlink reception time of frame 821 at UE 802. Additionally, Figure 800 includes the UE Rx-Tx time difference (UE Rx-Tx time difference). Rx-Tx (For example, t) 811 -t 814 ) and base station Rx-Tx time difference (gNB) Rx-Tx (For example, t)812 -t 813 Figure 800 also depicts the third symbol of time slot n (e.g., in t). 811 (at) and the third symbol in time slot n+1 (e.g., in t) 813 (Location).

[0081] like Figure 8 As shown, in some aspects, the difference or threshold of the Rx-Tx time difference can trigger Rx-Tx time difference transmission. To use the difference of the Rx-Tx time difference to determine whether the propagation delay has changed, this disclosure may include a strong relationship between the transmission times of the base station and the UE. For example, t2–t1 may be equal to a predefined value; that is, this disclosure may allow the UE to transmit a signal at a symbol in a certain time slot (e.g., the third symbol of time slot n), and the base station may transmit a signal at a symbol in another time slot (e.g., the third symbol of time slot n+1), where t2–t1 equals one time slot.

[0082] Additionally, this disclosure allows for the use of path loss changes to trigger Rx-Tx time difference transmission. Furthermore, timing advance (TA) adjustments can trigger Rx-Tx time difference transmission. Additionally, mobility events (e.g., UE mobility or handover) can trigger Rx-Tx time difference transmission.

[0083] As indicated above, the difference or threshold of the Rx-Tx time difference or path loss variation can trigger Rx-Tx time difference transmission. In these respects, if the base station determines that the Rx-Tx difference (e.g., t3–t2) or the uplink path loss variation exceeds a predefined threshold, the base station can send the Rx-Tx time difference (e.g., t3–t2) to the UE. The base station can also automatically send the Rx-Tx time difference to the UE. Once the UE receives the Rx-Tx difference (e.g., t3–t2), the UE can determine whether the time difference (e.g., t3–t2) exceeds a predefined threshold and whether propagation delay compensation can be calculated.

[0084] Additionally, if the base station determines that the Rx-Tx difference (e.g., t3–t2) or uplink path loss change exceeds a predefined threshold, the UE can send the Rx-Tx time difference (e.g., t4–t1) to the base station. When the time difference (e.g., the difference between t3 and t2 or the uplink path loss) exceeds a predefined threshold, and another time difference (e.g., the difference between t4 and t1) or downlink path loss at the UE may not exceed the threshold, the base station can send a signaling instruction to notify the UE to send the Rx-Tx time difference (e.g., t4–t1), and then perform propagation delay compensation. If available uplink resources exist, a (1) bit can be added to the PDCCH to indicate whether Rx-Tx time difference transmission is required. For example, if the bit is "1", the UE can send the Rx-Tx time difference to the base station. Furthermore, if available uplink resources exist and the PDCCH has 24 cyclic redundancy period (CRC) bits, a mask can be used to indicate whether Rx-Tx time difference transmission is required. If the base station requests the UE to send the Rx-Tx time difference, the base station can add a mask to several CRC bits (e.g., the last 6 CRC bits). Furthermore, if available uplink resources exist, MAC-CE can be used to indicate whether the Rx-Tx time difference may be needed.

[0085] In other aspects, if no uplink resources are available, the base station can send an uplink grant to the UE. For example, one bit in the uplink grant could indicate the transmission of the Rx-Tx time difference. Furthermore, if no uplink resources are available, the base station can send an uplink grant to the UE without any indicating bits. For example, the UE can use the allocated resources to autonomously transmit the Rx-Tx time difference.

[0086] In some aspects, if the UE determines that the Rx-Tx time difference (e.g., t4–t1) or downlink path loss change exceeds a predefined threshold, the base station can send the Rx-Tx time difference (e.g., t3–t2) to the UE. If the time difference (e.g., the difference between t4 and t1) or downlink path loss exceeds a predefined threshold, but the difference between t3 and t2 or the uplink path loss at the base station does not exceed a predefined threshold, the UE can send a signaling instruction to notify the base station that t3–t2 ​​transmission may be needed. If available uplink resources exist, the UE can send a MAC-CE to the base station to notify that Rx-Tx time difference transmission may be needed. Furthermore, if available uplink resources exist, a bit can be added to the UCI. For example, if the bit is "1", the base station can send the Rx-Tx time difference to the UE. If no available uplink resources exist, the UE can send an SR to notify the base station that Rx-Tx time difference transmission may be needed.

[0087] Additionally, if the UE determines that the Rx-Tx time difference (e.g., t4–t1) or downlink path loss change exceeds a predefined threshold, the UE can send the Rx-Tx time difference (e.g., t4–t1) to the base station. If available uplink resources exist, the UE can automatically send the Rx-Tx time difference to the base station. Once the base station receives the time difference information (e.g., t4–t1), it can determine whether the time difference information (e.g., t4–t1) exceeds a predefined threshold and whether propagation delay compensation may be necessary. If no available uplink resources exist, the UE can send an SR to notify the base station whether Rx-Tx time difference transmission may be required.

[0088] As indicated above, TA adjustment or mobility events (e.g., UE mobility or handover) can trigger Rx-Tx time difference transmission. If the TA adjustment exceeds a predefined threshold or a mobility or handover occurs, the base station can send the Rx-Tx time difference (e.g., t3–t2) to the UE. For example, the base station can automatically send the Rx-Tx time difference to the UE.

[0089] Additionally, if the TA adjustment exceeds a predefined threshold or a mobility or handover occurs, the UE can send the Rx-Tx time difference (e.g., t4–t1) to the base station. If available uplink resources exist, the UE can automatically send the Rx-Tx time difference to the base station. If no available uplink resources exist, the UE can send an SR to request resources for Rx-Tx time difference transmission. Furthermore, if no available uplink resources exist, the base station can send an uplink grant to allow the UE to send the Rx-Tx time difference. In some instances, the base station may not wait for the UE to send an SR.

[0090] Figure 9 Figure 900 shows an example communication between UE 902 and base station 904.

[0091] At 910, base station 904 can send an SPS to the UE via RRC signaling (e.g., SPS 914). At 912, UE 902 can receive an SPS from the base station via RRC signaling (e.g., SPS 914).

[0092] At point 920, UE 902 can determine the time difference between UE receive (Rx) and transmit (Tx) (Rx-Tx), where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. At point 922, base station 904 can determine the time difference between base station receive (Rx) and transmit (Tx) (Rx-Tx), where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time.

[0093] At 930, base station 904 can send a PDCCH to the UE (e.g., PDCCH 934), where the PDCCH indicates whether to send the base station's Rx-Tx time difference or to receive the UE's Rx-Tx time difference. At 932, UE 902 can monitor and receive the PDCCH from the base station (e.g., PDCCH 934), where the PDCCH indicates whether to send the UE's Rx-Tx time difference or to receive the base station's Rx-Tx time difference.

[0094] At position 940, UE 902 can determine whether at least one uplink resource is available for transmission. In some instances, when at least one uplink resource is available for transmission, a Media Access Control (MAC) control element (MAC-CE), Physical Downlink Control Channel (PDCCH), Cyclic Redundancy Check (CRC) bitmask, or Uplink Control Information (UCI) can indicate whether to transmit the UE Rx-Tx time difference or receive the base station Rx-Tx time difference. Furthermore, when at least one uplink resource is unavailable for transmission, a Scheduling Request (SR) or Uplink Grant can indicate whether to transmit the UE Rx-Tx time difference.

[0095] At position 950, UE 902 can send the UE Rx-Tx time difference to the base station or receive the base station Rx-Tx time difference from the base station (e.g., time difference 954), where the base station Rx-Tx time difference is equal to the difference between the uplink subframe reception time and the downlink subframe transmission time. At position 952, base station 904 can send the base station Rx-Tx time difference to the UE or receive the UE Rx-Tx time difference from the UE (e.g., time difference 954), where the UE Rx-Tx time difference is equal to the difference between the downlink subframe reception time and the uplink subframe transmission time. In some aspects, RRC signaling can indicate whether the UE Rx-Tx time difference is sent or received from the base station Rx-Tx time difference.

[0096] At point 960, when receiving the base station Rx-Tx time difference from the base station, UE 902 can calculate the propagation delay value, where the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference. At point 962, when receiving the UE Rx-Tx time difference from the UE, base station 904 can calculate the propagation delay value, where the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference. The base station Rx-Tx time difference can be received via the SPS Physical Downlink Shared Channel (PDSCH).

[0097] At position 970, when the UE Rx-Tx time difference is sent to the base station, UE 902 can receive a propagation delay value from the base station (e.g., propagation delay value 974), where the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference. At position 972, when the base station Rx-Tx time difference is sent to the UE, base station 904 can receive a propagation delay value from the UE (e.g., propagation delay value 974), where the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference.

[0098] In some aspects, the UE Rx-Tx time difference can be transmitted via an uplink configured permission (CG). The UE Rx-Tx time difference can be based on a predefined time offset between the physical (PHY) layer and an RRC message or a Media Access Control (MAC) control element (MAC-CE). The UE Rx-Tx time difference can be based on disabling scheduling requests (SRs) for one or more RRC messages or one or more MAC control elements (MAC-CEs). Furthermore, the UE Rx-Tx time difference can be based on a scheduling request (SR) delay timer. Additionally, the UE Rx-Tx time difference can be based on at least one logical channel.

[0099] In some instances, the UE Rx-Tx time difference can be sent or received via RRC messages or a Media Access Control (MAC) control element (MAC-CE). The UE Rx-Tx time difference can be sent when it exceeds a UE Rx-Tx time difference threshold, or received when the base station Rx-Tx time difference exceeds a base station Rx-Tx time difference threshold. Furthermore, the UE Rx-Tx time difference can be sent when uplink path loss exceeds an uplink path loss threshold, or received when downlink path loss exceeds a downlink path loss threshold. Additionally, the UE Rx-Tx time difference can be sent or received when timing advance (TA) adjustment exceeds a TA adjustment threshold. The UE Rx-Tx time difference can also be sent or received based on at least one of UE mobility or handover.

[0100] Figure 10This is a flowchart 1000 of a wireless communication method. The method can be performed by a UE or a component of a UE (e.g., UE 104, 350, 902; device 1202; processing system, which may include memory 360 and may be the entire UE or a component of a UE, such as TX processor 368, controller / processor 359, transmitter 354TX, antenna 352, etc.). Optional aspects are shown using dashed lines. The method described herein can provide numerous benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0101] At position 1002, the device can receive SPS from the base station via RRC signaling, such as in combination with Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1002 can be performed by determining component 1240.

[0102] At position 1004, the device can determine the UE receive (Rx) transmit (Tx) time difference. The UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time, such as when combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1004 can be performed by determining component 1240.

[0103] At position 1006, the device can monitor and receive PDCCH from the base station, where the PDCCH indicates whether the UE is sending or receiving the base station's Rx-Tx time difference, such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1006 can be performed by determining component 1240.

[0104] At point 1008, the device can determine whether at least one uplink resource is available for transmission, such as in combination with Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1008 can be performed by determining component 1240. In some instances, when at least one uplink resource is available for transmission, a Media Access Control (MAC) control element (MAC-CE), Physical Downlink Control Channel (PDCCH), Cyclic Redundancy Check (CRC) bitmask, or Uplink Control Information (UCI) can indicate whether to transmit the UE Rx-Tx time difference or receive the base station Rx-Tx time difference, as combined with... Figure 4 , 5AThe examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, when at least one uplink resource is unavailable for transmission, a scheduling request (SR) or uplink grant can indicate whether to transmit the UE Rx-Tx time difference, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0105] At position 1010, the device can send the UE Rx-Tx time difference to the base station or receive the base station Rx-Tx time difference from the base station. The base station Rx-Tx time difference is equal to the difference between the uplink subframe reception time and the downlink subframe transmission time, such as when combined with... Figure 4 , 5A Examples described in 5B, 6A, 6B, 7A, 7B, 8, and 9. For example, 1010 can be performed by determining component 1240. In some aspects, RRC signaling can indicate whether to send the UE Rx-Tx time difference or receive the base station Rx-Tx time difference, as combined with Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0106] At position 1012, when receiving the base station Rx-Tx time difference from the base station, the device can calculate the propagation delay value, where the propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference, as combined with... Figure 4 , 5A Examples described in 5B, 6A, 6B, 7A, 7B, 8, and 9. For example, 1012 can be performed by determining component 1240. The base station Rx-Tx time difference can be received via the SPS physical downlink shared channel (PDSCH), as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0107] At position 1014, when the UE Rx-Tx time difference is sent to the base station, the device can receive the propagation delay value from the base station. This propagation delay value is equal to the sum of the UE Rx-Tx time difference and the base station Rx-Tx time difference. (This is combined with...) Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1014 can be performed by determining component 1240.

[0108] In some aspects, the UE Rx-Tx time difference can be transmitted via uplink configured permission (CG), such as in combination with Figure 4 , 5AThe examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. The UE Rx-Tx time difference can be based on a predefined time offset between the physical (PHY) layer and the RRC message or Media Access Control (MAC) control element (MAC-CE), such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. The UE Rx-Tx time difference can be based on disabling scheduling requests (SRs) for one or more RRC messages or one or more Media Access Control (MAC) Control Elements (MAC-CEs), as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, the UE Rx-Tx time difference can be based on a scheduling request (SR) delay timer, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, the UE Rx-Tx time difference can be based on at least one logical channel, such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0109] In some instances, the UERx-Tx time difference can be sent or the base station Rx-Tx time difference can be received via RRC messages or a Media Access Control (MAC) control element (MAC-CE), such as in combination with... Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. When the UE Rx-Tx time difference exceeds the UE Rx-Tx time difference threshold, the UE Rx-Tx time difference can be transmitted; or when the base station Rx-Tx time difference exceeds the base station Rx-Tx time difference threshold, the base station Rx-Tx time difference can be received, as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, when the uplink path loss exceeds the uplink path loss threshold, the UE Rx-Tx time difference can be transmitted, or when the downlink path loss exceeds the downlink path loss threshold, the base station Rx-Tx time difference can be received, as in combination with... Figure 4 , 5A The examples described in 5B, 6A, 6B, 7A, 7B, 8, and 9 illustrate this. Furthermore, when the timing advance (TA) adjustment exceeds the TA adjustment threshold, the UE can transmit the Rx-Tx time difference or receive the base station's Rx-Tx time difference, as in combination with... Figure 4 , 5AAs described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. Based on at least one of UE mobility or handover, the UE Rx-Tx time difference can also be transmitted, or the base station Rx-Tx time difference can also be received, as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0110] Figure 11 This is a flowchart 1100 of a wireless communication method. The method can be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 904; device 1302; processing system, which may include memory 376 and may be the entire base station or a component of a base station, such as antenna 320, receiver 318RX, RX processor 370, controller / processor 375, etc.). Optional aspects are shown using dashed lines. The method described herein can provide numerous benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0111] At 1102, the device can send an SPS to the UE via Radio Resource Control (RRC) signaling, such as in combination with Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1102 can be performed by the determining component 1340.

[0112] At point 1104, the device can determine the base station receive (Rx) transmit (Tx) time difference. The base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time, such as when combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1104 can be performed by the determining component 1340.

[0113] At position 1106, the device can send a Physical Downlink Control Channel (PDCCH) to the UE. The PDCCH indicates whether the base station is transmitting the Rx-Tx time difference or receiving the UE's Rx-Tx time difference, such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1106 can be performed by the determining component 1340.

[0114] At point 1108, the device can send the base station Rx-Tx time difference to the UE or receive the UE Rx-Tx time difference from the UE. The UE Rx-Tx time difference is equal to the difference between the downlink subframe reception time and the uplink subframe transmission time, such as when combined with... Figure 4 , 5AThe examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1108 can be performed by determining component 1340. RRC signaling can indicate whether to transmit the base station Rx-Tx time difference or receive the UE Rx-Tx time difference, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0115] At point 1110, when receiving the UE Rx-Tx time difference from the UE, the device can calculate the propagation delay value, where the propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. For example, 1110 can be performed by determining component 1340. The UE Rx-Tx time difference can be received via uplink configured permission (CG), as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0116] The UE Rx-Tx time difference can be based on a predefined time offset between the physical (PHY) layer and RRC messages or Media Access Control (MAC) control elements (MAC-CE), such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. The UE Rx-Tx time difference can be based on disabling scheduling requests (SRs) for one or more RRC messages or one or more Media Access Control (MAC) Control Elements (MAC-CEs), as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, the UE Rx-Tx time difference can be based on a scheduling request (SR) delay timer, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. Furthermore, the UE Rx-Tx time difference can be based on at least one logical channel, such as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0117] At point 1112, when the base station Rx-Tx time difference is sent to the UE, the device can receive the propagation delay value from the UE. This propagation delay value is equal to the sum of the base station Rx-Tx time difference and the UE Rx-Tx time difference. (This is combined with...) Figure 4 , 5AExamples described in 5B, 6A, 6B, 7A, 7B, 8, and 9. For example, 1112 can be performed by determining component 1340. The base station Rx-Tx time difference can be transmitted via the SPS physical downlink shared channel (PDSCH), as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0118] In some aspects, the base station Rx-Tx time difference can be sent or the UE Rx-Tx time difference can be received via RRC messages or Media Access Control (MAC) control elements (MAC-CE), such as in combination with Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. When the base station Rx-Tx time difference exceeds the base station Rx-Tx time difference threshold, the base station Rx-Tx time difference can be transmitted; or when the UE Rx-Tx time difference exceeds the UE Rx-Tx time difference threshold, the UE Rx-Tx time difference can be received, as in combination with... Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. When the downlink path loss exceeds the downlink path loss threshold, the base station Rx-Tx time difference can be transmitted; or when the uplink path loss exceeds the uplink path loss threshold, the UE Rx-Tx time difference can be received, as in combination with... Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. When the timing advance (TA) adjustment exceeds the TA adjustment threshold, the base station can transmit the Rx-Tx time difference or receive the UERx-Tx time difference, as combined with... Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. Based on at least one of UE mobility or handover, the base station Rx-Tx time difference can be transmitted, or the UE Rx-Tx time difference can be received, as in combination with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0119] Furthermore, it can be determined that at least one uplink resource is available for transmission or is not available for transmission, such as in combination with Figure 4 , 5AThe examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 describe this. When at least one uplink resource is available for transmission, the Media Access Control (MAC) control element (MAC-CE), Physical Downlink Control Channel (PDCCH), Cyclic Redundancy Check (CRC) bitmask, or Uplink Control Information (UCI) can indicate whether the base station is transmitting the Rx-Tx time difference or receiving the UE's Rx-Tx time difference, as combined with... Figure 4 , 5A As described in examples 5B, 6A, 6B, 7A, 7B, 8, and 9. When at least one uplink resource is unavailable for transmission, a scheduling request (SR) or uplink grant can indicate whether to receive the UE Rx-Tx time difference, as combined with... Figure 4 , 5A The examples in 5B, 6A, 6B, 7A, 7B, 8, and 9 are described.

[0120] Figure 12Figure 1200 illustrates an example of a hardware implementation for device 1202. Device 1202 is a UE and includes a cellular baseband processor 1204 (also referred to as a modem) coupled to a cellular RF transceiver 1222 and one or more Subscriber Identity Module (SIM) cards 1220, an application processor 1206 coupled to a Secure Digital (SD) card 1208 and a screen 1210, a Bluetooth module 1212, a Wireless Local Area Network (WLAN) module 1214, a Global Positioning System (GPS) module 1216, and a power supply 1218. The cellular baseband processor 1204 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1222. The cellular baseband processor 1204 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1204 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1204, the software causes the cellular baseband processor 1204 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1204 during software execution. The cellular baseband processor 1204 also includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes one or more of the components shown. The components within the communication manager 1232 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1204. The cellular baseband processor 1204 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1202 can be a modem chip and only include the baseband processor 1204, and in another configuration, the device 1202 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1202.

[0121] The communication manager 1232 includes a determining component 1240 configured to receive semi-persistent scheduling (SPS) from a base station via Radio Resource Control (RRC) signaling, for example, as described above in conjunction with step 1002. The determining component 1240 can also be configured to determine the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time, for example, as described above in conjunction with step 1004. The determining component 1240 can also be configured to transmit the UE Rx-Tx time difference to the base station or receive the base station Rx-Tx time difference from the base station, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time, for example, as described above in conjunction with step 1010.

[0122] The apparatus may include execution Figure 9 and 10 The additional components of each box in the algorithm's flowchart above. Therefore, Figure 9 and 10 Each block in the above flowchart can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0123] In one configuration, apparatus 1202 (and in particular, cellular baseband processor 1204) includes: a unit for receiving semi-persistent scheduling (SPS) from a base station via Radio Resource Control (RRC) signaling. Apparatus 1202 may further include: a unit for determining the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, the UE Rx-Tx time difference being equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. Apparatus 1202 further includes: a unit for transmitting the UE Rx-Tx time difference to the base station or a unit for receiving the base station Rx-Tx time difference from the base station, the base station Rx-Tx time difference being equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. The aforementioned units may be one or more components of apparatus 1202 configured to perform the functions described above. As described above, apparatus 1202 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned units may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described above.

[0124] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1302. Device 1302 is a base station and includes a baseband unit 1304. Baseband unit 1304 can communicate with UE 104 via a cellular RF transceiver. Baseband unit 1304 may include computer-readable medium / memory. Baseband unit 1304 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by baseband unit 1304, the software causes baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1304 when executing the software. Baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. Communication manager 1332 includes one or more of the components shown. Components within communication manager 1332 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1304. The baseband unit 1304 may be a component of the BS 310 and may include at least one of the TX processor 316, the RX processor 370 and the controller / processor 375 and / or the memory 376.

[0125] The communication manager 1332 includes a determining component 1340 configured to send a semi-persistent schedule (SPS) to the user equipment (UE) via radio resource control (RRC) signaling, for example, as described above in conjunction with step 1102. The determining component 1340 can also be configured to determine a base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, where the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time, for example, as described above in conjunction with step 1104. The determining component 1340 can also be configured to send the base station Rx-Tx time difference to the UE or receive the UE Rx-Tx time difference from the UE, where the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time, for example, as described above in conjunction with step 1108.

[0126] The apparatus may include execution Figure 9 and 11 The additional components of each box in the algorithm's flowchart above. Therefore, Figure 9 and 11 Each block in the above flowchart can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0127] In one configuration, apparatus 1302 (and in particular, baseband unit 1304) includes: a unit for transmitting semi-persistent scheduling (SPS) to user equipment (UE) via radio resource control (RRC) signaling. Apparatus 1302 further includes: a unit for determining the base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, the base station Rx-Tx time difference being equal to the difference between the uplink subframe receive time and the downlink subframe transmit time. Apparatus 1302 further includes: a unit for transmitting the base station Rx-Tx time difference to the UE or for receiving the UE Rx-Tx time difference from the UE, the UE Rx-Tx time difference being equal to the difference between the downlink subframe receive time and the uplink subframe transmit time. The aforementioned units may be one or more components of apparatus 1302 configured to perform the functions described above. As described above, apparatus 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described above.

[0128] It is to be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It is to be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of the various boxes in the order shown and are not intended to be limited to the specific order or hierarchy given.

[0129] The preceding description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the textual claims, wherein, unless expressly stated otherwise, reference to a singular element is not intended to mean “one and only one,” but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. For example, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure that are known to or will later become known to a person skilled in the art are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms "module", "mechanism", "element", "device", etc., may not be a substitute for the term "unit". Thus, no claim element is to be interpreted as a functional unit unless the element is expressly recited using the phrase "unit for...".

Claims

1. A method for wireless communication at a user equipment (UE): Semi-persistent scheduling (SPS) is received from the base station via Radio Resource Control (RRC) signaling; Determine the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, wherein the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time; as well as The UE Rx-Tx time difference is sent to the base station or received from the base station based at least in part on the SPS and / or one or more triggering events, wherein the base station Rx-Tx time difference is equal to the difference between the uplink subframe reception time and the downlink subframe transmission time.

2. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: Semi-persistent scheduling (SPS) is received from the base station via Radio Resource Control (RRC) signaling; Determine the UE receive (Rx) transmit (Tx) (Rx-Tx) time difference, wherein the UE Rx-Tx time difference is equal to the difference between the downlink subframe receive time and the uplink subframe transmit time; as well as The UE Rx-Tx time difference is sent to the base station or received from the base station based at least in part on the SPS and / or one or more triggering events, wherein the base station Rx-Tx time difference is equal to the difference between the uplink subframe reception time and the downlink subframe transmission time.

3. The apparatus according to claim 2, wherein, The RRC signaling indicates whether to send the UE's Rx-Tx time difference or to receive the base station's Rx-Tx time difference.

4. The apparatus according to claim 2, wherein, The at least one processor is further configured to: Monitor the Physical Downlink Control Channel (PDCCH) from the base station; and The PDCCH is received from the base station, wherein the PDCCH indicates whether the UE is sending the Rx-Tx time difference or receiving the Rx-Tx time difference from the base station.

5. The apparatus according to claim 2, wherein, In order to receive the Rx-Tx time difference of the base station, the at least one processor is configured to receive the Rx-Tx time difference of the base station from the base station, wherein the at least one processor is further configured to: Calculate the propagation delay value, wherein the propagation delay value is equal to the sum of the Rx-Tx time difference of the UE and the Rx-Tx time difference of the base station.

6. The apparatus according to claim 5, wherein, In order to receive the base station Rx-Tx time difference, the at least one processor is configured to receive the base station Rx-Tx time difference via the SPS Physical Downlink Shared Channel (PDSCH).

7. The apparatus according to claim 2, wherein, In order to transmit the UE Rx-Tx time difference, the at least one processor is configured to transmit the UE Rx-Tx time difference to the base station, wherein the at least one processor is further configured to: The propagation delay value is received from the base station, wherein the propagation delay value is equal to the sum of the Rx-Tx time difference of the UE and the Rx-Tx time difference of the base station.

8. The apparatus according to claim 7, wherein, In order to transmit the UE Rx-Tx time difference, the at least one processor is configured to transmit the UE Rx-Tx time difference via an uplink configured permission (CG).

9. The apparatus according to claim 8, wherein, The UE Rx-Tx time difference is based on a predefined time offset between the physical (PHY) layer and the RRC message or media access control (MAC) control element (MAC-CE).

10. The apparatus according to claim 8, wherein, The UE Rx-Tx time difference is based on disabling scheduling requests (SRs) for one or more RRC messages or one or more Media Access Control (MAC) Control Elements (MAC-CEs).

11. The apparatus according to claim 8, wherein, The UE Rx-Tx time difference is based on a scheduling request (SR) delay timer or at least one logical channel.

12. The apparatus according to claim 2, wherein, The one or more triggering events include the UE Rx-Tx time difference exceeding the UE Rx-Tx time difference threshold or the base station Rx-Tx time difference exceeding the base station Rx-Tx time difference threshold.

13. The apparatus according to claim 2, wherein, The one or more triggering events include downlink path loss exceeding a downlink path loss threshold, or uplink path loss exceeding an uplink path loss threshold.

14. The apparatus according to claim 2, wherein, The one or more triggering events include a timed advance (TA) adjustment exceeding the TA adjustment threshold.

15. The apparatus according to claim 2, wherein, The one or more triggering events include at least one of UE mobility or handover.

16. The apparatus according to claim 2, wherein, The at least one processor is further configured to: Determine whether at least one uplink resource is available for transmission.

17. The apparatus according to claim 16, wherein, When at least one uplink resource is available for transmission, the Media Access Control (MAC) control element (MAC-CE), Physical Downlink Control Channel (PDCCH), Cyclic Redundancy Check (CRC) bitmask, or Uplink Control Information (UCI) indicates whether to send the UE Rx-Tx time difference or receive the base station Rx-Tx time difference.

18. The apparatus according to claim 16, wherein, When at least one uplink resource is unavailable for transmission, a scheduling request (SR) or uplink grant indication is sent to determine whether the UE Rx-Tx time difference is transmitted.

19. The apparatus according to claim 2, wherein, The UE Rx-Tx time difference is sent via an RRC message or a Media Access Control (MAC) control element (MAC-CE), or the base station Rx-Tx time difference is received via an RRC message or a MAC-CE.

20. An apparatus for wireless communication at a user equipment (UE), comprising: A unit used to receive semi-persistent scheduling (SPS) from a base station via radio resource control (RRC) signaling; A unit for determining the time difference between UE reception (Rx) and transmission (Tx) (Rx-Tx), wherein the UE Rx-Tx time difference is equal to the difference between the downlink subframe reception time and the uplink subframe transmission time; as well as A unit for transmitting the UE Rx-Tx time difference to the base station based at least in part on the SPS and / or one or more triggering events, or a unit for receiving the base station Rx-Tx time difference from the base station, wherein the base station Rx-Tx time difference is equal to the difference between the uplink subframe reception time and the downlink subframe transmission time.

21. A method for wireless communication at a base station, comprising: Semi-persistent scheduling (SPS) is sent to the user equipment (UE) via Radio Resource Control (RRC) signaling; Determine the base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, wherein the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time; as well as At least in part based on the SPS and / or one or more triggering events, the base station Rx-Tx time difference is sent to the UE or received from the UE, the UE Rx-Tx time difference being equal to the difference between the downlink subframe reception time and the uplink subframe transmission time.

22. An apparatus for wireless communication at a base station, comprising: Memory; as well as At least one processor, coupled to the memory, is configured to: Semi-persistent scheduling (SPS) is sent to the user equipment (UE) via Radio Resource Control (RRC) signaling; Determine the base station receive (Rx) transmit (Tx) (Rx-Tx) time difference, wherein the base station Rx-Tx time difference is equal to the difference between the uplink subframe receive time and the downlink subframe transmit time; as well as At least in part based on the SPS and / or one or more triggering events, the base station Rx-Tx time difference is sent to the UE or received from the UE, the UE Rx-Tx time difference being equal to the difference between the downlink subframe reception time and the uplink subframe transmission time.

23. The apparatus according to claim 22, wherein, The RRC signaling indicates whether to send the base station's Rx-Tx time difference or to receive the UE's Rx-Tx time difference.

24. The apparatus according to claim 22, wherein, The at least one processor is further configured to: Send a Physical Downlink Control Channel (PDCCH) to the UE, wherein the PDCCH indicates whether to send the Rx-Tx time difference of the base station or to receive the Rx-Tx time difference of the UE.

25. The apparatus according to claim 22, wherein, In order to transmit the base station Rx-Tx time difference, the at least one processor is configured to transmit the base station Rx-Tx time difference to the UE, wherein the at least one processor is further configured to: The propagation delay value is received from the UE, wherein the propagation delay value is equal to the sum of the Rx-Tx time difference of the base station and the Rx-Tx time difference of the UE.

26. The apparatus according to claim 25, wherein, In order to transmit the base station Rx-Tx time difference, the at least one processor is configured to transmit the base station Rx-Tx time difference via the SPS Physical Downlink Shared Channel (PDSCH).

27. The apparatus according to claim 22, wherein, In order to receive the UE Rx-Tx time difference, the at least one processor is configured to receive the UE Rx-Tx time difference from the UE, wherein the at least one processor is further configured to: Calculate the propagation delay value, wherein the propagation delay value is equal to the sum of the Rx-Tx time difference of the base station and the Rx-Tx time difference of the UE.

28. The apparatus according to claim 27, wherein, In order to receive the UE Rx-Tx time difference, the at least one processor is configured to receive the UE Rx-Tx time difference via an uplink configured permission (CG).

29. The apparatus according to claim 28, wherein, The UE Rx-Tx time difference is based on a predefined time offset between the physical (PHY) layer and the RRC message or media access control (MAC) control element (MAC-CE).

30. The apparatus according to claim 28, wherein, The UE Rx-Tx time difference is based on disabling scheduling requests (SRs) for one or more RRC messages or one or more Media Access Control (MAC) Control Elements (MAC-CEs).

31. The apparatus according to claim 28, wherein, The UE Rx-Tx time difference is based on a scheduling request (SR) delay timer or at least one logical channel.

32. The apparatus according to claim 22, wherein, The one or more triggering events include the base station Rx-Tx time difference exceeding the base station Rx-Tx time difference threshold or the UE Rx-Tx time difference exceeding the UE Rx-Tx time difference threshold.

33. The apparatus according to claim 22, wherein, The one or more triggering events include uplink path loss exceeding the uplink path loss threshold or downlink path loss exceeding the downlink path loss threshold.

34. The apparatus according to claim 22, wherein, The one or more triggering events include a timed advance (TA) adjustment exceeding the TA adjustment threshold.

35. The apparatus according to claim 22, wherein, The base station Rx-Tx time difference is sent via an RRC message or a Media Access Control (MAC) control element (MAC-CE), or the UE Rx-Tx time difference is received via an RRC message or a MAC-CE.

Images