Dynamic timing advance (TA) indication in downlink control information (DCI)

Abstract

This disclosure provides systems, methods, and apparatus, including computer programs encoded on a computer storage medium, for dynamic timing advance (TA) indication in downlink control information (DCI). The described techniques relate to indicating a TA command in a DCI message. For a DCI message configured to schedule uplink or downlink communications, one or more fields of the DCI message may be reused and populated with a value indicating that the DCI message includes a TA command and indicating the TA command itself. A user equipment (UE) may communicate an uplink message to the network according to the indicated TA command. The TA command may indicate a timing adjustment value or an absolute TA value relative to a previous TA. The DCI message may indicate whether the TA command is a relative TA adjustment or an absolute TA adjustment.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, including dynamic timing advance indication in downlink control information. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (such as time, frequency and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations (BS) or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0004] One innovative aspect of the subject matter described in the present disclosure can be implemented in a method for wireless communication at a user equipment (UE). The method includes: receiving a downlink control information (DCI) message, the downlink control information (DCI) message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format including a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; and sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0005] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a UE. The apparatus includes one or more interfaces configured to: obtain a DCI message, the DCI message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being filled with a value indicating that the DCI message includes a timing advance command; and output an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0006] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a UE. The apparatus includes: a component for receiving a DCI message, the DCI message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; and a component for sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0007] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a UE. The code includes instructions executable by a processor to perform the following operations: receiving a DCI message, the DCI message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being filled with a value indicating that the DCI message includes a timing advance command; and sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DCI message may include operations, features, components, or instructions for receiving an uplink DCI message, wherein the uplink DCI message indicates the timing advance command rather than a scheduling uplink shared channel message or a grant (CG) configuration for activating or releasing a configuration.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DCI message may include operations, features, components, or instructions for receiving a downlink DCI message, wherein the downlink DCI message indicates the timing advance command rather than scheduling a downlink shared channel message or activating or releasing a semi-persistent scheduling (SPS) configuration.

[0010] One innovative aspect of the subject matter described in the present disclosure can be implemented in a method for wireless communication at a network entity. The method includes: sending a DCI message to a UE, the DCI message including one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; and receiving an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0011] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a network entity. The apparatus includes one or more interfaces configured to: output a DCI message to a UE, the DCI message including one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being filled with a value indicating that the DCI message includes a timing advance command; and obtain an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0012] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a network entity. The apparatus includes: a component for sending a DCI message to a UE, the DCI message including one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; and a component for receiving an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0013] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a network entity. The code includes instructions executable by a processor to perform the following operations: send a DCI message to a UE, the DCI message including one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being filled with a value indicating that the DCI message includes a timing advance command; and receive an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the DCI message may include operations, features, components, or instructions for sending an uplink DCI message, wherein the uplink DCI message indicates the timing advance command rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the DCI message may include operations, features, components, or instructions for sending a downlink DCI message, wherein the downlink DCI message indicates the timing advance command rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0016] Details of one or more specific implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Note that the relative dimensions in the drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 An example of a wireless communication system that supports dynamic timing advance (TA) indication in downlink control information (DCI) is shown.

[0018] Figure 2 An example of a network architecture supporting dynamic TA indication in DCI is illustrated.

[0019] Figure 3 An example of a signaling diagram to support dynamic TA indication in DCI is illustrated.

[0020] Figure 4 An example of a timing diagram supporting dynamic TA indication in DCI is illustrated.

[0021] Figure 5 An example of a timing diagram supporting dynamic TA indication in DCI is illustrated.

[0022] Figure 6 An example of a timing diagram supporting dynamic TA indication in DCI is illustrated.

[0023] Figure 7 An example of a resource map supporting dynamic TA indication in DCI is illustrated.

[0024] Figure 8 An example of a resource map supporting dynamic TA indication in DCI is illustrated.

[0025] Fig. 9 An example of a resource map supporting dynamic TA indication in DCI is illustrated.

[0026] Fig.10 An example of a process flow to support dynamic TA indication in DCI is illustrated.

[0027] Fig.11 A diagram of a system including devices supporting dynamic TA indication in DCI is shown.

[0028] Fig.12 A diagram of a system including devices supporting dynamic TA indication in DCI is shown.

[0029] Fig.13 and Fig.14 A flow chart illustrating a method of supporting dynamic TA indication in DCI is shown.

[0030] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION

[0031] For the purpose of describing the innovative aspects of the present disclosure, the following description refers to some specific implementations. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described specific implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals in accordance with any one of the Institute of Electrical and Electronics Engineers (IEEE) 16.11 standards or any one of the following: IEEE 802.11 standards, Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM or General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or other known signals for communicating within a wireless, cellular or Internet of Things (IOT) network, such as a system utilizing third generation (3G) technology, fourth generation (4G) technology, or fifth generation (5G) technology, or further specific implementations thereof.

[0032] In some wireless communication systems, a user equipment (UE) may receive downlink control information (DCI) from multiple transmission and reception points (TRPs) and schedule uplink transmissions (such as physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) transmissions) to multiple TRPs. The UE may distinguish TRPs based on the control resource set (CORESET) pool index associated with the TRP. The UE may adjust the timing of the uplink transmission by applying a timing advance (timing advance (TA) value) to the uplink transmission, which means that the timing of the uplink transmission may be "advanced" by the amount indicated by the TA value. The UE may apply different TAs to uplink transmissions to different TRPs. The initial TA value may be indicated in a random access response (RAR) message, or an absolute TA command may be indicated in a medium access control (MAC) control element (CE). After the initial TA, the network may indicate additional, increased TA adjustments to the UE in a TA command. The TA adjustment may be indicated to the UE via a MAC-CE. However, indication via MAC-CE is less flexible than indication via DCI and may be associated with higher latency. However, there is currently no defined way to include the TA command in a DCI message, or to indicate in a DCI message that the DCI message carries the TA command. There is also currently no defined way to indicate to which CORESET pool index (such as to which TRP) the TA command in a DCI message applies.

[0033] The present disclosure relates to a technique for indicating a TA command in a DCI message. For a DCI message configured to schedule uplink or downlink communications, one or more fields of the DCI message may be repurposed and filled with a value indicating that the DCI message includes a TA command and the TA command itself. For example, the DCI format may include a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI). The UE may communicate an uplink message to the network according to the indicated TA command. Example fields that may be used to indicate that the DCI message includes a TA command, and fields that may actually include a TA command, such as a time domain resource allocation (TDRA) field, a hybrid automatic repeat request (HARQ) process number (HPN) field, a frequency hopping flag field, a transmit power control (TPC) field, a PUCCH resource indicator field, or a physical downlink shared channel (PDSCH) to HARQ timing indicator field. The DCI message may also indicate a CORESET pool index and a component carrier (CC) to which the TA command applies. Depending on the time slot in which the DCI message is received, the UE may be selected, calculated, or determined to be a later time slot in which the TA command becomes applicable. The TA command may indicate a timing adjustment value relative to a previous TA or an absolute TA value. The DCI message may indicate whether the TA command is a relative TA adjustment or an absolute TA adjustment.

[0034] Certain implementations of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. Since DCI messages are more flexible and faster than MAC-CE, by using DCI messages to indicate a TA command, the TA command may be more flexible and communicated to the UE in a faster manner than the TA command communicated to the UE via MAC-CE. By setting a given field to a defined value, a DCI message configured for scheduling communications between the UE and the network may be reused to indicate a TA command, and thus, the TA command may be indicated with the speed and flexibility of a DCI message without defining a new type of DCI message.

[0035] Figure 1 An example of a wireless communication system 100 that supports dynamic TA indication in DCI is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some implementations, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0036] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some implementations, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125, such as radio frequency (RF) access links. For example, the network entities 105 may support a coverage area 110, such as a geographic coverage area, over which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area in which the network entities 105 and the UEs 115 may support signal communications according to one or more radio access technologies (RATs).

[0037] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communications with other UEs 115 or network entities 105) as shown.

[0038] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (such as any network entity described herein), a UE 115 (such as any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0039] In some implementations, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (such as according to S1, N2, N3, or other interface protocols). In some implementations, the network entities 105 may communicate with each other via the backhaul communication links 120 (such as according to X2, Xn, or other interface protocols) directly (such as directly between the network entities 105) or indirectly (such as via the core network 130). In some implementations, the network entities 105 may communicate with each other via the midhaul communication links 162 (such as according to the midhaul interface protocol) or the fronthaul communication links 168 (such as according to the fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (such as electrical links, optical fiber links), one or more wireless links (such as radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0040] One or more of the network entities 105 described herein may include or may be referred to as a base station (BS) 140 (such as a transceiver base station, a radio BS, an NR BS, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a giga-Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some specific implementations, the network entity 105 (such as BS 140) may be implemented in an aggregated (such as a monolithic, standalone) BS architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (such as a single RAN node, such as BS 140).

[0041] In some implementations, the network entity 105 may be implemented in a disaggregated architecture, such as a disaggregated BS architecture, a disaggregated RAN architecture, which may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) such as a network configuration sponsored by the O-RAN Alliance, or a virtualized RAN (vRAN) such as a cloud RAN (C-RAN). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 such as a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (such as separate physical locations). In some implementations, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (such as virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0042] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (such as network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack, and DU 165 may support one or more different layers of a protocol stack. In some implementations, CU 160 may host higher protocol layer (such as layer 3 (L3), layer 2 (L2)) functionality and signaling (such as radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (such as a physical (PHY) layer) or L2 (such as a radio link control (RLC) layer, a MAC layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (such as via one or more RUs 170). In some implementations, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (such as some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (such as F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (such as an open fronthaul (FH) interface). In some implementations, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on interfaces (such as channels) between layers of a protocol stack supported by respective network entities 105 that communicate via these communication links.

[0043] In some wireless communication systems (such as wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (such as to core network 130). In some specific implementations, in an IAB network, one or more network entities 105 (such as IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (such as donor BS 140). One or more donor network entities 105 (such as IAB donors) may communicate with one or more additional network entities 105 (such as IAB nodes 104) via supported access and backhaul links (such as backhaul communication links 120). IAB nodes 104 may include IAB mobile terminations (IAB-MTs) controlled (such as scheduling) by DUs 165 of coupled IAB donors. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (such as the RU 170) for access via the DU 165 of the IAB node 104 (such as referred to as a virtual IAB-MT (vIAB-MT)). In some implementations, the IAB node 104 may include a DU 165 that supports communication links with additional entities (such as the IAB node 104, UE 115) within a relay chain or configuration (such as downstream) of the access network. In such implementations, one or more components of the decomposed RAN architecture (such as one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0044] For example, an access network (AN) or RAN may include access nodes (such as an IAB donor), communications between the IAB node 104 and one or more UEs 115. The IAB donor may facilitate a connection between the core network 130 and the AN (such as via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (such as and RU 170), and the CU 160 may communicate with the core network 130 via an interface (such as a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (such as an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (such as CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0045] An IAB node 104 may refer to a RAN node that provides IAB functionality, such as access for UE 115, wireless self-backhaul capabilities, etc. The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (such as an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104 , and a DU interface such as DU 165 may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115 .

[0046] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (such as a backhaul communication link 120), and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 via the IAB node 104, or may directly signal the UE 115 to transmit, or both. The CU 160 of the IAB donor may signal the IAB node 104 to establish a communication link via the F1 interface, and the IAB node 104 may schedule the transmission (such as the transmission relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0047] In a specific implementation of the techniques described herein applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support dynamic TA indication in a DCI as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (such as a BS 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (such as an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0048] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some specific implementations, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0049] like Figure 1As shown, the UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay BSs, etc.

[0050] The UE 115 and the network entity 105 may communicate with each other wirelessly via one or more communication links 125 (such as access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (such as a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (such as LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling (such as synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink CCs and one or more uplink CCs according to the carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) CCs. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (such as an entity, a sub-entity) of the network entity 105. For example, the terms "send", "receive" or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (such as BS 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (such as directly or via one or more other network entities 105).

[0051] In some implementations (such as in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (such as an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, where a UE 115 may perform initial acquisition and connection via a carrier, or a carrier may operate in a non-standalone mode, anchoring a connection using a different carrier (such as the same or different radio access technology).

[0052] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (such as forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (such as return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink or uplink communications (such as in an FDD mode) or may be configured to carry downlink and uplink communications (such as in a TDD mode).

[0053] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some implementations, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (such as 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (such as the network entity 105, the UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configurable to support communications using one of a set of carrier bandwidths. In some implementations, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some implementations, each served UE 115 may be configured to operate using a portion (such as a subband, BWP) or all of a carrier bandwidth.

[0054] The signal waveform transmitted via the carrier may include multiple subcarriers (such as using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of a symbol period (such as the duration of a modulation symbol) and a subcarrier, and the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (such as the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (such as within the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (such as spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0055] One or more parameter sets for a carrier may be supported, and the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some implementations, a UE 115 may be configured with multiple BWPs. In some implementations, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to one or more active BWPs.

[0056] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit. In some implementations, the basic time unit may refer to a sampling period T s =1 / (Δf max ·N f ) seconds, its Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specific duration, such as 10 milliseconds (ms). Each radio frame may be identified by a system frame number, such as ranging from 0 to 1023.

[0057] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some implementations, a frame may be divided into subframes (such as in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (such as, depending on the length of the cyclic prefix added in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (such as N) time slots. f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0058] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (such as in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some implementations, the TTI duration (such as the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (such as in bursts of shortened TTIs (sTTIs)).

[0059] Physical channels may be multiplexed using carriers for communication according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region for a physical control channel, such as a control resource set (CORESET), may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions, such as CORESETs, may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources, such as control channel elements (CCEs), associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0060] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (such as using a carrier), and may be associated with an identifier used to distinguish adjacent cells (such as a physical cell identifier (PCID), a virtual cell identifier (VCID), or other). In some specific implementations, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (such as a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (such as structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0061] A macro cell typically covers a relatively large geographic area (such as a radius of several kilometers) and may allow unrestricted access to UEs 115 with service subscriptions to a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (such as lower power BSs 140) than macro cells, and small cells may operate using the same or different (such as licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 with service subscriptions to a network provider, or may provide restricted access to UEs 115 associated with small cells (such as UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office, etc.). The network entity 105 may support one or more cells, and may also support communications via one or more cells using one or more CCs.

[0062] In some implementations, a carrier may support multiple cells, and different cells may be configured according to different protocol types that may provide access to different types of devices, such as MTC, narrowband IoT (NB-IoT), and enhanced mobile broadband (eMBB).

[0063] In some implementations, the network entities 105 (such as BS 140, RU 170) can be mobile and thus provide communication coverage for mobile coverage areas 110. In some implementations, different coverage areas 110 associated with different technologies can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0064] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (such as BS 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some implementations, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0065] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines, such as via machine-to-machine (M2M) communication. M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105, such as BS 140, without human intervention. In some implementations, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0066] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (such as a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some implementations, half-duplex communication may be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (such as according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range within a carrier, within a guard band of a carrier, or outside a carrier (such as a set of subcarriers or resource blocks (RBs)).

[0067] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0068] In some implementations, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (such as according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some implementations, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (such as a BS 140, RU 170), which may support various aspects of such D2D communication configured (such as scheduling) by the network entity 105. In some implementations, one or more UEs 115 of the group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some implementations, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some implementations, the network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving the network entity 105.

[0069] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (such as UE 115). In some specific implementations, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicle can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some specific implementations, the vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communication, or communicate with the network via one or more network nodes (such as network entity 105, BS140, RU170), or both.

[0070] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (such as a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (such as a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (such as BS 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0071] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (such as less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0072] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as a centimeter band, or using an extremely high frequency (EHF) region of the spectrum (such as from 30 GHz to 300 GHz), also known as a millimeter band. In some specific implementations, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (such as BS140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some specific implementations, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmission may be affected by greater attenuation and shorter range than SHF or UHF transmission. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

[0073] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entities 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some specific implementations, operations using unlicensed bands may be based on a carrier aggregation configuration combined with a CC operating in a licensed band (such as LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0074] The network entity 105 (such as BS140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to adopt technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication or beamforming. The antennas of the network entity 105 or UE115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more BS antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some specific implementations, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0075] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (such as the same codeword) or different data streams (such as different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0076] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (such as a network entity 105, a UE 115) to shape or direct an antenna beam (such as a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include a transmitting device or a receiving device applying an amplitude offset, a phase offset, or both to a signal carried via an antenna element associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (such as relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0077] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (such as BS 140, RU 170) may use multiple antennas or antenna arrays (such as antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (such as by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by the network entity 105.

[0078] Some signals (such as data signals associated with a particular receiving device) may be sent by a transmitting device (such as a transmitting network entity 105, a transmitting UE 115) along a single beam direction (such as a direction associated with a receiving device such as a receiving network entity 105 or a receiving UE 115). In some implementations, a beam direction associated with transmission along a single beam direction may be selected, calculated, or determined based on signals sent along one or more beam directions. For example, a UE 115 may receive one or more of the signals sent by the network entity 105 along different directions, and may report to the network entity 105 an indication of the signal received by the UE 115 with the highest signal quality or other acceptable signal quality.

[0079] In some implementations, transmission by a device (such as by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (such as from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. The network entity 105 may transmit a reference signal (such as a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or not precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (such as a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (such as BS 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (such as for identifying a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (such as for sending data to a receiving device).

[0080] A receiving device (such as UE 115) may perform receiving operations according to multiple receiving configurations (such as directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (such as network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (such as different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some implementations, a receiving device may use a single receiving configuration to receive along a single beam direction (such as when receiving a data signal). A single receive configuration may be aligned along a beam direction selected, calculated, or determined based on listening according to different receive configuration directions, such as a beam direction selected, calculated, or determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions.

[0081] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly to communicate via logical channels. The MAC layer can perform priority processing and multiplexing of logical channels into transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of the RRC connection that supports the radio bearer of user plane data between the UE115 and the network entity 105 or the core network 130. The PHY layer can map the transport channel to the physical channel.

[0082] UE 115 and network entity 105 may support retransmission of data to increase the possibility of data being successfully received. HARQ feedback is a technique for increasing the possibility of correctly receiving data via a communication link (such as communication link 125, D2D communication link 135). HARQ may include a combination of error detection (such as using CRC), forward error correction (FEC) and retransmission (such as automatic repeat request (ARQ)). HARQ can improve the throughput of the MAC layer under poor radio conditions (such as low signal-to-noise ratio conditions). In some specific implementations, the device may support the same time slot HARQ feedback, for which the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0083] Figure 2 An example of a network architecture 200 (such as a decomposed BS architecture, a decomposed RAN architecture) supporting per-TRP power control parameters is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly communicate with the core network 130-a through one or more decomposed network entities 105 (such as, a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (such as, an SMO framework), or both. The CU 160- may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (such as an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served simultaneously by multiple RUs 170-a.

[0084] Each of the network entities 105 of the network architecture 200 (such as CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (such as data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (such as a controller) that provides instructions to the interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on the wired transmission medium or send signals to one or more of the other network entities 105 on the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission medium, or to send signals to one or more network entities in other network entities 105 via a wireless transmission medium, or both.

[0085] In some specific implementations, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (such as CU-UP), control plane functionality (such as CU-CP), or a combination thereof. In some specific implementations, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0086] DU 165-a may correspond to a logical unit that includes one or more functions (such as BS functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some implementations, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (such as a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional splits, such as those defined by the Third Generation Partnership Project (3GPP). In some implementations, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0087] In some implementations, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some implementations, such a configuration may enable the implementation of the DU 165-a and CU 160-a in a cloud-based RAN architecture (such as a vRAN architecture).

[0088] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180- may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network entities 105, the SMO 180- may be configured to interact with a cloud computing platform (such as O-Cloud 205) via a cloud computing platform interface (such as an O2 interface) to perform network entity lifecycle management (such as to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to the 4G RAN (such as via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0089] The non-RT RIC 175-a may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (such as via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b.

[0090] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some implementations, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (such as via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0091] In some implementations, UE 115-a may communicate with the network via multiple TRPs (such as UE 115-a may operate in a multi-TRP mode). As described herein, a TRP may include RU 170-a, DU 165-a, or a combination thereof.

[0092] Figure 3 An example of a signaling diagram 300 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the signaling diagram 300 can implement aspects of the wireless communication system 100. The signaling diagram 300 can include a UE 115-b, which can be an example of a UE 115 as described herein. The signaling diagram 300 can include a network entity 105-a, which can be an example of a network entity 105 as described herein.

[0093] UE 115-b may operate in a multi-TRP mode with a first TRP 305-a and a second TRP 305-b. In some implementations, the first TRP 305-a and the second TRP 305-b may be located at the same network entity 105-a. In some implementations, the first TRP 305-a and the second TRP 305-b may be located at different network entities.

[0094] UE 115-b may communicate with the first TRP 305-a and the second TRP 305-b. In some implementations, UE 115-b may be able to communicate with the first TRP 305-a and the second TRP 305-b simultaneously (such as using the same time resource set, or the same frequency resource set, or both, but using different spatial resources). UE 115-b may communicate with the first TRP 305-a using communication link 125-b. UE 115-b may communicate with the second TRP 305-b using communication link 125-c. Communication link 125-b and communication link 125-c may include a bidirectional link that implements both uplink communication and downlink communication. For example, UE 115-b may use communication link 125-b to send an uplink signal 330-a, such as an uplink control signal or an uplink data signal, to the first TRP 305-a, and the first TRP 305-a may use communication link 125-b to send a downlink signal 335-a, such as a downlink control signal or a downlink data signal, to UE 115-b. UE 115-b may use communication link 125-c to send an uplink signal 330-b, such as an uplink control signal or an uplink data signal, to the second TRP 305-b, and the second TRP 305-b may use communication link 125-c to send a downlink signal 335-b, such as a downlink control signal or a downlink data signal, to UE 115-b. In some specific implementations, different TRPs (such as the first TRP 305-a and the second TRP 305-b) may have different TRP identifiers. In some implementations, different TRPs may be identified by association with other identifiers, such as a CORESET pool index, a closed loop index, a transmission configuration indicator (TCI) identifier, a TCI group identifier, or a sounding reference signal resource set identifier.

[0095] UE 115-b can support multi-TRP transmission operation based on multiple DCI. In multi-TRP operation based on multiple DCI, a first DCI message (sent from a first TRP 305-a) can schedule a first PDSCH sent from a first TRP 305-a via a communication link 125-b, and a second DCI message (sent from a second TRP 305-b) can schedule a second PDSCH sent from a second TRP 305-b via a communication link 125-c. The TRP difference on the UE side can be associated with a CORESET pool index. Each CORESET (up to 5 core sets) can be configured with a value of a parameter CORESETPoolIndex, which can be "0" or "1". Therefore, the CORESET can be divided into two groups. In addition to the CORESET pool index, the TRP (the first TRP 305-a and the second TRP 305-b) can be transparent to UE 115-b. UE 115-d can configure multi-TRP operation based on multiple DCI in a given CC.

[0096] In some implementations, the UE may be configured via a higher layer parameter PDCCH-Config that includes two different values ​​of the parameter CORESETPoolIndex in the CORESET of the active BWP of the serving cell. For example, CORESETPoolIndex = "0" may include a CORESET identifier equal to "1" and a CORESET identifier equal to "2", and CORESETPoolIndex = "1" may include a CORESET identifier equal to "3" and a CORESET identifier equal to "4". The CORESETPoolIndex of the CORESET in which the DCI is received may be used for different purposes, such as HARQ feedback.

[0097] In some implementations, each serving cell may be associated with a TA group (TAG). Figure 4 As described, two TA values ​​for uplink multi-DCI multi-TRP operation may be specified. For example, two TAGs may be specified, and each TRP may be associated with a different TAG.

[0098] In some implementations, the initial TA value for uplink transmission 315 may be indicated by a RAR 310 PDSCH transmission or an absolute MAC-CE 320 command. TA may be a positive absolute value ranging from TA=0, 1, 2, ..., 3846. The value of TA may be converted to a time offset, such as N TA =TA 16·64 / 2 μ. The NTA may be relative to the subcarrier spacing of the first uplink transmission from the UE 115-b after receipt of the RAR 310 PDSCH or absolute TA command MAC-CE 320. After the first TA command, the network entity 105-a may send a TA adjustment value (such as an adjustment for changes in the location or channel conditions of the UE 115-b). The TA adjustment value may be indicated via the MAC-CE 320. The MAC-CE 320 may indicate a TAG identifier. The adjustment of the current NTA value (NTA_old) to the new NTA value (NTA_new) may be indicated in the MAC-CE 320 by an index value, which is TA=0, 1, 2, ..., 63, where for 2 μ 15kNz subcarrier spacing, N TA_新 =N TA_旧 +(T A -31)·16·64 / 2 μ For a TA command n received on an uplink timeslot and for a transmission other than a PUSCH scheduled by a RAR 310 including an uplink grant, a fallback RAR 310 including an uplink grant, or a PUCCH with HARQ acknowledgement (ACK) information in response to a successful RAR 310, a corresponding adjustment of the uplink transmission timing may be made from uplink timeslot n+k+1+2 μ ·K 偏移 The start application, where When additional PDSCH demodulation reference signals are configured, N T,1 Refers to the duration in milliseconds of N1 symbols corresponding to the PDSCH processing time of UE 115-b processing capability 1. T,2 Refers to the duration in milliseconds of N2 symbols corresponding to the PUSCH preparation time of UE 115-b processing capability 1. N1 and N2 may be selected, calculated, or determined relative to the minimum subcarrier spacing of all configured uplink BWPs of all uplink carriers in the TAG and the subcarrier spacing of all configured downlink BWPs of the corresponding downlink carriers. For μ=0, UE 115-b may assume that N 1,0 =14. TA,最大 refers to the maximum TA value in milliseconds that can be provided by the 12-bit TA command field, and n TA,最大 The minimum subcarrier spacing may be selected, calculated or determined relative to the subcarrier spacing of all uplink carriers in the TAG and all configured initial uplink BWPs provided by the parameter initialUplinkBWP. Can refer to the number of time slots per subframe, T sf It can refer to a subframe duration of 1 millisecond. Time slot n and The minimum subcarrier spacing among the subcarrier spacings of all configured uplink BWPs of all uplink carriers in the TAG may be selected, calculated or determined. 偏移 =K 小区,时隙 -K UE,偏移 , where K 小区,偏移 Provided by Koffset in ServingCellConfigCommon, and K UE,偏移 Provided by MAC CE command; otherwise, if not provided separately, K 小区,偏移 =0 or K UE,偏移 = 0. Uplink time slot n refers to the time slot for PDSCH reception. Assume that T TA = 0 The last time slot of the overlapping uplink time slots, where PDSCH provides TA command and T TA It may be a defined value known to the UE 115-b and the network entity 105-a. Figure 5 An example illustration of TA application time is described.

[0099] In some implementations, the dedicated DCI message 325 may indicate a TA adjustment value for a given TRP, such as the first TRP 305-a or the second TRP 305-b. For example, when the UE 115-b receives the TA command in the DCI message 325, the UE 115-b may adjust the uplink transmit timing associated with the given TRP by the corresponding TA adjustment value. For example, the TA adjustment value range may be [-31·16·64 / 2 μ , 32·16·64 / 2 μ In another example, the TA command in the MAC-CE 320 may indicate a timing adjustment value for the uplink transmission 315-a to the first TRP 305-a, and the TA instruction in the DCI message may indicate an offset value between the TA adjustment value for the uplink transmission 315-b to the second TRP 305-b and the TA adjustment value for the first TRP 305-a. For example, the MAC-CE 320 may indicate a TA adjustment index value T for the uplink transmission 315-a to the first TRP 305-a. A , and the DCI message 325 may indicate an offset value Δ 偏移 , and the TA adjustment value of the uplink transmission 315-b to the second TRP 305-b may be (T A -31)·16·64 / 2 μ +Δ 偏移As another example, the TA command in the DCI message 325 may indicate an offset value between a currently maintained TA of one TRP (such as the first TRP 305-a) and an expected TA of another TRP (such as the second TRP 305-b). For example, the TA of the uplink transmission 315-a to the first TRP 305-a may be maintained as N TA1 , and when UE 115-b receives in DCI message 325 an uplink transmission 315-b with index value T to a second TRP 305-b TA,偏移 When the TA command is given, the TA of the second TRP 305-b can be calculated as N TA2 =N TA1 +T TA,偏移 ·16·64 / 2 μ , and T TA,偏移 It can be positive or negative. Assuming that the maximum uplink timing difference of inter-band carrier aggregation is applied to multi-TRP operation based on multi-DCI, the range T of frequency range 1 (FR1) (34.6us) TA,偏移 It can be [-66·2 μ ,66·2 μ ], and the frequency range 2 (FR2) (8.5us) can be in the range of [-16·2 μ , 16.2 μ ].

[0100] For multi-TRP operation based on multi-DCI, the TA command in the dedicated DCI message 325 may indicate a TA adjustment value for a given CORESETPoolIndex value, a TA adjustment offset value of a TA adjustment offset relative to a reference CORESETPoolIndex value (such as a TA adjustment value of an uplink transmission 315 associated with a reference CORESETPoolIndex value which may be indicated via MAC-CE 320), or a TA offset value of a TA value relative to a reference CORESETPoolIndex value (such as a TA value of a of a reference CORESETPoolIndex value which may be indicated via MAC-CE 320).

[0101] Compared to MAC-CE, DCI messages can be faster and more flexible. Additionally, the application of the TA indication of the DCI message to the uplink channel can be selected, calculated, ascertained or determined at UE 115-b based on the CORESETPoolIndex of the CORESET in which the DCI message is received. However, one issue is how to indicate that the DCI message includes a TA command.

[0102] In some implementations, an uplink DCI message 340 or a downlink DCI message 345 (such as a DCI message having multiple fields configured to indicate scheduling information for uplink or downlink transmissions, respectively) may be reused to indicate a TA command. For example, the uplink DCI message 340 or the downlink DCI message 345 may include a CRC scrambled by the CS-RNTI.

[0103] For example, an uplink DCI message 340 (fallback or non-fallback) that can be used to indicate a TA command may not schedule a PUSCH, or may not activate or release a configured grant (CG). For the uplink DCI message 340, the CS-RNTI may be used for CRC scrambling. A given field of the uplink DCI message 340 may be set to indicate that the uplink DCI message 340 carries a TA command. For example, the redundancy version (RV) field may be all set to "1", the modulation and control scheme (MCS) field may be all set to "1", and the new data indicator (NDI) field may be set to "0". The frequency domain resource allocation (FDRA) field may be set to "0" for type 0 or dynamically switched FDRA, or to "1" for FDRA type 1. The RV, MCS, NDI, and FDRA fields may be used to indicate that the uplink DCI message 340 includes a TA command, because the RV, MCS, NDI, and FDRA fields are not used for uplink scheduling. The TA command itself in the uplink DCI message 340 may be indicated using one or more of the TDRA field (including 4 bits), the HPN field (including 4 bits), the frequency hopping flag field (including 1 bit), or the TPC field (including 2 bits).

[0104] As another example, a downlink DCI message 345 (fallback or non-fallback) that can be used to indicate a TA command may not schedule a PDSCH, or may not activate or release a semi-persistent scheduling (SPS) PDSCH. For the downlink DCI message 345, the CS-RNTI may be used for CRC scrambling. A given field of the downlink DCI message 345 may be set to indicate that the downlink DCI message carries a TA command. For example, the RV field may be set to all "1", the MCS field may be set to all "1", and the NDI field may be set to "0". The FDRA field may be set to "0" for type 0 or dynamically switched FDRA, or to "1" for FDRA type 1. Additionally, the HPN field may be set to all "1" to distinguish that the downlink DCI message 345 is used for a TA command rather than a unified TCI state. The TA command itself in the downlink DCI message 345 can be indicated using one or more of the TDRA field, the TPC command for the scheduled PUCCH (including 2 bits), the PUCCH resource indicator (including 3 bits), or the PDSCH to HARQ feedback timing indicator (including 3 bits).

[0105] In some implementations, the TAG identifier may be included in a TA command in a DCI message (either an uplink DCI message 340 or a downlink DCI message 345), and the TA command in the DCI message (either an uplink DCI message 340 or a downlink DCI message 345) may be applied to CCs configured with the same TAG identifier as the indicated TAG identifier. For example, in some implementations, a single TA may be applied per CC. In some implementations, multiple TAs may be applied per CC, where each CC is configured with multiple TAG identifiers. In such implementations where each CC is configured with multiple TAG identifiers, if the CC is configured with multiple CORESETPoolIndex values ​​(such as multi-TRP operation based on multi-DCI), the TA command may be applied to uplink transmissions 315 associated with the same CORESETPoolIndex value associated with the indicated TAG identifier. In some implementations, multiple TAs may be applied per CC, where each CC is configured with a single TAG identifier. In such a specific implementation, where multiple TAs may be applied to each CC and where each CC is configured with a single TAG identifier, if the CC is configured with multiple CORESETPoolIndex values ​​(such as multi-TRP operation based on multi-DCI), the TA command may be applied to uplink transmissions 315 associated with the same CORESETPoolIndex value associated with the CORESET in which the uplink DCI message 340 or the downlink DCI message 345 is received.

[0106] In some implementations, the CC to which the TA applies may be selected, calculated, ascertained, or determined using a carrier indicator field (CIF) in a DCI message (uplink DCI message 340 or downlink DCI message 345). If the CIF is present in the DCI message (uplink DCI message 340 or downlink DCI message 345), the CIF indicates the CC, and the TA command may be applied to the TAG identifier configured for the indicated CC. If the CIF is not present in the uplink DCI message 340 or downlink DCI message 345 (such as in an implementation without cross-carrier scheduling or for fallback DCI), the TA command may be applied to the TAG identifier configured for the default uplink CC. The default uplink CC may be assumed to be an uplink CC associated with the downlink CC in which the DCI message (uplink DCI message 340 or downlink DCI message 345) is received. In an implementation where the CC is configured with multiple CORESETPoolIndex values ​​and multiple TAG identifiers, the TA command may apply to the TAG identifier associated with the same CORESETPoolIndex value associated with the CORESET in which the DCI message (uplink DCI message 340 or downlink DCI message 345) is received. In an implementation where the CC is configured with multiple CORESETPoolIndex values ​​and a single TAG (but supports multiple TAs), the TA command may apply to the uplink transmission 315 associated with the same CORESETPoolIndex value associated with the CORESET in which the DCI message (uplink DCI message 340 or downlink DCI message 345) is received.

[0107] For a TA command received in a DCI message (either uplink DCI message 340 or downlink DCI message 345) received in uplink timeslot n, and for a transmission other than: a PUSCH scheduled by a RAR uplink grant or a fallback RAR uplink grant; or a PUCCH with HARQ-ACK information in response to a successful RAR, the corresponding adjustment of the uplink transmission 315 is from uplink timeslot n+k+1+2 μ ·K 偏移 The start application, where N T,1 The duration in milliseconds of N symbols corresponding to the SPS PDSCH release processing time of UE 115-b processing capability 1. T,2Refers to the duration in milliseconds of N2 symbols corresponding to the PUSCH preparation time of the UE 115-b processing capability. N and N2 may be selected, calculated, or determined relative to the minimum subcarrier spacing among the subcarrier spacing of all configured uplink BWPs of all uplink carriers in the TAG and the subcarrier spacing of all configured downlink BWPs of the corresponding downlink carriers. N TA,最大 Refers to the maximum TA value in milliseconds that can be provided by the 12-bit TA Command field and can be selected, calculated or determined relative to the minimum subcarrier spacing among the subcarrier spacings of all uplink carriers in the TAG and all configured initial uplink BWPs provided by the parameter initialUplinkBWP. Refers to the number of time slots in each subframe. sf Refers to the duration of a subframe of 1 millisecond. Time slot n and The minimum subcarrier spacing among the subcarrier spacings of all configured uplink BWPs of all uplink carriers in the TAG may be selected, calculated or determined. 偏移 =K 小区,偏移 -K UE,偏移 , where K 小区,偏移 Provided by the Koffset in the ServingCellConfigCommon field, and K UE,偏移 Provided by MAC-CE command. If K 小区,偏移 and K UE,偏移 If not provided separately, K 小区,偏移 =0 or K UE,偏移 = 0. In some implementations, the uplink time slot n may be based on the time slot assumption T received on the physical downlink control channel (PDCCH). TA = 0 to select, calculate, ascertain or determine the last time slot of the overlapping uplink time slots, where the PDCCH provides a TA command, and T TA It may be a defined value known to the UE 115-b and the network entity 105-a. In some implementations, the uplink time slot n may be based on a symbol hypothesis T received with the PDCCH. TA = 0 to select, calculate, ascertain or determine the last time slot of the overlapping uplink time slots, where the PDCCH provides a TA command, and T TA It may be a defined value known to the UE 115 - b and the network entity 105 - a .

[0108] In some embodiments, UE 115-b may be configured with multiple CORESETPoolIndex values, and to select, calculate, or determine the TA value for a given uplink transmission 315, one of the following options may be indicated by a DCI message (uplink DCI message 340 or downlink DCI message 345) that includes a TA command: (1) a timing adjustment value for a given CORESETPoolIndex value, (2) a timing adjustment offset value for a timing adjustment offset relative to a reference CORESETPoolIndex value, or (3) a TA offset value for a TA value relative to a reference CORESETPoolIndex value.

[0109] Figure 4 An example of a timing diagram 400 for supporting dynamic TA indication in a DCI is illustrated. In some implementations, the timing diagram 400 can implement aspects of the wireless communication system 100 or the signaling diagram 300. For example, the timing diagram 400 can include a UE 115-c, which can be an example of a UE 115 as described herein. TRP1 and TRP2 can be examples of a first TRP 305-a and a second TRP 305-b, as described in reference to FIG. Figure 3 described.

[0110] In some implementations, separate uplink timing may be applied to a multi-TRP deployment, where a first TA value (such as t1) is applied to communications between UE 115-c and TRP 1, and a second TA value (such as t2) is applied to communications between UE 115-c and TRP 2. Thus, two TAs may be specified, and each TRP (TRP1 and TRP2) may have a different TA value (such as specified via a TAG value).

[0111] Figure 5 An example of a timing diagram 500 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the timing diagram 500 can implement aspects of the wireless communication system 100 or the signaling diagram 300.

[0112] UE 115 may operate in accordance with multi-DCI multi-TRP operation as described herein. UE 115 may operate in accordance with multi-DCI multi-TRP operation as described herein. 偏移 = 0, operating with a downlink subcarrier spacing of 15 kHz and an uplink subcarrier spacing of 30 kHz. In this specific implementation, the reference subcarrier spacing for N1 and N2 may be 15 kHz, which corresponds to N1 = 14 symbols, N2 = 10 symbols, and N T,1 =1ms, N T,2 =0.71ms. For N TA,最大 The reference subcarrier spacing may be 30 kHz, which corresponds to N TA,最大 = 1ms. For time slot n and The reference subcarrier spacing may be 30 kHz, which corresponds to Thus, when UE 115 receives PDSCH 510 carrying MAC-CE with TA command 515 on a downlink timeslot that overlaps uplink timeslot 0 and timeslot 1, timeslot 1 may correspond to timeslot n. The offset 520 after the TA command is applied may be calculated as k+1+2 μ ·K 偏移 = 8 time slots. Therefore, the TA command 515 received in time slot 0 and time slot 1 will be applied to time slot 9 first.

[0113] Figure 6 An example of a timing diagram 600 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the timing diagram 500 can implement aspects of the wireless communication system 100 or the signaling diagram 300.

[0114] UE 115 may operate in accordance with multi-DCI multi-TRP operation as described herein. UE 115 may operate in accordance with multi-DCI multi-TRP operation as described herein. 偏移 = 0, operating with a downlink subcarrier spacing of 15 kHz and an uplink subcarrier spacing of 30 kHz. In this specific implementation, the reference subcarrier spacing for N and N2 may be 15 kHz, which corresponds to N = 10 and N2 = 10, corresponding to N T,1 =0.71ms, N T,2 =0.71ms. For N TA,最大 The reference subcarrier spacing may be 30 kHz, which corresponds to N TA,最大 = 1ms. For time slot n and The reference subcarrier spacing may be 30 kHz, which corresponds to therefore, Therefore, the offset 620 after the TA command is applied can be based on k+2 μ ·K 偏移 =6 time slots to select, calculate, ascertain or determine.

[0115] UE 115 receives DCI message 610 including a TA command in time slot 0. In a specific implementation that may select, calculate, ascertain, or determine uplink time slot n based on the last time slot of the uplink time slots that overlaps with the time slot of the PDCCH in which the DCI message 610 is transmitted, time slot 1 corresponds to time slot n, so assuming offset 620 is equal to 6 time slots, the TA indicated in TA command 615 is applicable to time slot 8. In a specific implementation that may select, calculate, ascertain, or determine uplink time slot n based on the last time slot of the uplink time slots that overlaps with the symbol of the PDCCH in which the DCI message 610 is transmitted, time slot 0 corresponds to time slot n, so assuming offset 620 is equal to 6 time slots, the TA indicated in TA command 615 is applicable to time slot 7.

[0116] Figure 7 An example of a resource map 700 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the resource map 700 can implement aspects of the wireless communication system 100 or the signaling map 300.

[0117] As described herein, to indicate a TA adjustment value for a given CORESETPoolIndex value, the TA adjustment index value for the uplink associated with the CORESETPoolIndex value may be indicated by one or more bit fields in an uplink DCI message or a downlink DCI message. In some implementations, the given CORESETPoolIndex may be the same as the CORESETPoolIndex of the CORESET receiving the uplink DCI.

[0118] In some implementations, a given CORESETPoolIndex may be the same as the CORESETPoolIndex associated with the indicated TAG identifier (such as in an implementation where two TAG identifiers are configured for the serving cell). The TA value associated with a given CORESETPoolIndex value may be based on the current TA value. and the TA adjustment value associated with a given CORESETPoolIndex value. For example, the new TA value T A,TRPx =0,1,2,3,...,63).

[0119] In some implementations, as shown in the uplink DCI example 705, the TAG identifier 710-a may be indicated in two bits of the TDRA field 720, and the TA adjustment index value 715-a (T A,TRPx) may be indicated in the remaining bits of the TDRA field 720 and in the bits of the HPN field 725. In some implementations, as shown in the downlink DCI example 750, the TAG identifier 710-b may be indicated in two bits of the TPC field 730, and the TA adjustment index value 715-b (T A,TRPx ) may be indicated in the bits of the PUCCH resource indicator (PRI) field 735 and the PDSCH to HARQ feedback timing indicator 740. In some implementations, the TAG identifier may not be included in the DCI message.

[0120] Figure 8 An example of a resource map 800 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the resource map 800 can implement aspects of the wireless communication system 100 or the signaling map 300.

[0121] As described herein, in order to indicate a TA adjustment offset value of an uplink transmission associated with a second CORESETPoolIndex value relative to a timing adjustment value of an uplink transmission associated with a reference CORESETPoolIndex value, the TA adjustment offset index value of the uplink transmission associated with the second CORESETPoolIndex may be indicated by a remaining field in an uplink DCI or a downlink DCI. The reference CORESETPoolIndex may be predefined (such as the lowest CORESETPoolIndex value 0) or RRC configured. A,TRP2 ) The TA adjustment index value associated with may be selected, calculated or determined as (T A,TRP2 =T A,TRP1 +(ΔT A -63), where T A,TRP1 refers to the TA adjustment index value associated with the reference CORESETPoolIndex value, and ΔT A Refers to the TA adjustment offset index value. ΔT A The step size can be predefined or configured, for example, if ΔT A The step size is 1, then ΔT A =0,1,2,3,...,126. With the second CORESETPoolIndex value ) The TA value associated with may be selected, calculated or determined as

[0122] In some implementations, as shown in the uplink DCI example 805, the TAG identifier 810-a may be indicated in two bits of the TDRA field 820-a, and the TA adjustment index value 815-a (T A,TRPx) may be indicated in the remaining bits of the TDRA field 820-a, bits of the frequency hopping flag field 830, and bits of the HPN field 825. In some implementations, as shown in the downlink DCI example 850, the TAG identifier 810-b may be indicated in two bits of the TDRA field 820-b, and the timing adjustment index value 815-a (T A,TRPx ) may be indicated in two bits of the TDRA field 820-b and bits of the TPC field 845 or the PRI or PDSCH to HARQ feedback timing indicator field 840. In some implementations, the TAG identifier may not be included in the DCI message.

[0123] Fig. 9 An example of a resource map 900 that supports dynamic TA indication in a DCI is illustrated. In some implementations, the resource map 900 can implement aspects of the wireless communication system 100 or the signaling map 300.

[0124] In order to indicate the TA offset value of the uplink transmission associated with the second CORESETPoolIndex value relative to the TA value of the reference CORESETPoolIndex value, the TA offset index value of the uplink transmission associated with the second CORESETPoolIndex value may be indicated by the remaining fields in the uplink DCI or downlink DCI. The reference CORESETPoolIndex may be predefined (such as the lowest CORESETPoolIndex value 0) or RRC configured.

[0125] For FR1, with the second CORESETPoolIndex value The associated TA value may be selected, calculated or determined as ΔT TA =[0,...,132·2 μ ], for FR2, ΔT TA =[0,...,32·2 μ ]. Refers to the N associated with the reference CORESETPoolIndex value TA value, and ΔT TA Refers to the TA offset index. ΔT TA The step size may be predefined or configured (such as RRC configured). For example, if μ = 0 and ΔT TA The step size is 1, then ΔT TA =0,1,2,3,...,132.

[0126] In some implementations, as shown in uplink DCI example 905, the TA offset index 915-a may be indicated in 4 bits of the TDRA field 920-a, bits of the frequency hopping flag field 930, and bits of the HPN field 925. The TAG identifier 910-a may be indicated in bits of the TPC field 945-a. In some implementations, as shown in downlink DCI example 950, the TA offset index 915-b may be indicated in 4 bits of the TDRA field 920-b, 2 bits of the TPC field 945-b, two bits of the PRI field 935, and one bit of the PDSCH to HARQ feedback timing indicator field 940. The TAG identifier 910-b may be indicated in two bits of the HARQ timing indicator field 940.

[0127] Fig.10 An example of a process flow 1000 for supporting dynamic TA indication in a DCI is illustrated. The process flow 1000 may include a UE 115-d, which may be an example of a UE 115 as described herein. The process flow 1000 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 1000, operations between the network entity 105-b and the UE 115-d may be sent in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-d may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 1000, and other operations may be added to the process flow 1000.

[0128] At 1005, the network entity 105-b may send a DCI message to the UE 115-d, the DCI message including one or more fields associated with scheduling information for communication between the UE 115-d and the network entity 105-b. The DCI message may be received in a DCI format that includes a CRC scrambled by the CS-RNTI, and one or more fields may be populated with a value indicating that the DCI message includes a TA command.

[0129] At 1010 , UE 115 - d may send an uplink message associated with the TA command indicated in the DCI message received at 1005 to a network entity.

[0130] In some embodiments, the DCI message is an uplink DCI message, and the uplink DCI message indicates a TA command rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0131] In some implementations, the DCI message is a downlink DCI message, and the downlink DCI message indicates a TA command instead of scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0132] In some implementations, sending the uplink message associated with the TA command includes applying the TA command to the uplink message, which is scheduled on one of the one or more CCs associated with the TAG identifier included in the TA command. In some implementations, sending the uplink message associated with the TA command also includes applying the TA command to the uplink message in one of the one or more CCs, which is associated with the TAG identifier included in the TA command. In some implementations, each of the one or more CCs is associated with a plurality of different TA commands having corresponding different TAG identifiers, and the UE 115-d further applies the TA command to the uplink message in one of the one or more CCs, which is associated with a CORESET pool index, which is also associated with the TAG identifier included in the TA command. In some implementations, each of the one or more CCs is associated with a plurality of different TA commands each associated with a TAG identifier, and the UE 115-d further applies the TA command to the uplink message in the one of the one or more CCs, which is associated with the CORESET pool index in which the DCI message is received.

[0133] In some implementations, sending an uplink message associated with a TA command includes applying the TA command to an uplink message scheduled in one of the one or more CCs, selecting one of the one or more CCs based on whether a CIF is present in the DCI message. In some implementations, where the CIF is present in the DCI message, the one of the one or more CCs may be associated with a TAG identifier associated with the CC indicated by the CIF. In some implementations, where the CIF is not present in the DCI message, the one of the one or more CCs may be associated with a TAG identifier associated with a default CC. In some implementations, the default CC may be an uplink CC associated with a downlink CC in which the DCI message is received. In some implementations, the uplink message in the one of the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is received.

[0134] In some implementations, the DCI message may be received in one or more symbols of a DCI receive slot, and the TA command may be applicable to a number of slots following a designated slot associated with the DCI receive slot, the number of slots being associated with an SPS PDSCH release processing capability of the UE 115-d. In some implementations, the designated slot may be a last slot in a plurality of uplink slots that overlap with the DCI receive slot. In some implementations, the designated slot may be a last slot in a set of a plurality of uplink slots that overlap with one or more symbols of the DCI receive slot.

[0135] In some implementations, where the TA command is a TA adjustment index value associated with a CORESET pool index, sending the uplink message associated with the TA command indicated in the DCI message further comprises sending the uplink message using a TA associated with a previous TA value associated with the CORESET pool index and the TA adjustment index value. In some implementations, the CORESET pool index is the same as the CORESET pool index in which the DCI message was received. In some implementations, the CORESET pool index is the same CORESET pool index as the CORESET pool index associated with the TAG identifier included in the DCI message.

[0136] In some implementations, where the TA command is a TA adjustment offset value associated with a first CORESET pool index and represents a TA offset relative to a TA adjustment value associated with a reference CORESET pool index, sending an uplink message associated with the TA command indicated in the DCI message further comprises sending the uplink message using a TA associated with a previous TA value associated with the first CORESET pool index, a TA adjustment value associated with the reference CORESET pool index, and a TA adjustment offset value associated with the first CORESET pool index. In some implementations, the UE 115-d may receive an indication of the reference CORESET pool index from the network entity 105-b.

[0137] In some implementations, where the TA command is a TA offset value associated with a first CORESET pool index and represents a TA offset relative to a TA value associated with a reference CORESET pool index, sending an uplink message associated with the TA command indicated in the DCI message further comprises sending the uplink message using a TA associated with a current TA value associated with the reference CORESET pool index and the TA offset value associated with the first CORESET pool index. In some implementations, the UE 115 - d may receive an indication of the reference CORESET pool index from the network entity 105 - b.

[0138] In some implementations, the one or more fields populated with values ​​indicating that the DCI message includes a TA command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0139] In some implementations, the TA command is indicated in at least one of a TDRA field, a HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0140] In some implementations, the TA command indicates a timing adjustment relative to a previous TA. In some implementations, the TA command indicates an absolute TA. In some implementations, one or more fields of the DCI message populated with a value indicating that the DCI message includes a TA command are not populated with a value indicating scheduling information for communication between the UE and the network entity.

[0141] Fig.11 A diagram of a system 1100 is shown that includes a device 1105 that supports dynamic TA indication in a DCI. The device 1105 may communicate with one or more network entities (such as one or more components of one or more BSs), one or more UEs 115, or any combination thereof (such as wirelessly). The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (such as operatively, communicatively, functionally, electronically, electrically) via one or more buses (such as a bus 1145).

[0142] I / O controller 1110 can manage input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some implementations, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some implementations, the I / O controller 1110 may be implemented as part of a processor or processing system (such as the processor 1140). In some implementations, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0143] In some implementations, the device 1105 may include a single antenna 1125. However, in some other implementations, the device 1105 may have more than one antenna 1125, which can concurrently send or receive multiple wireless transmissions. The transceiver 1115 can communicate bidirectionally via one or more antennas 1125, wired or wireless links, as described herein. For example, the transceiver 1115 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1125 for transmission, and for demodulating packets received from one or more antennas 1125. In some implementations, the transceiver 1115 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1125 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1125 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 1115 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations associated with received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1115, or the transceiver 1115 and one or more antennas 1125, or the transceiver 1115 and one or more antennas 1125 and one or more processors or memory components (such as the processor 1140 or the memory 1130 or both) may be included in a chip or chip component installed in the device 1105.

[0144] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code 1135 may not be directly executable by the processor 1140, but may cause the computer (such as when compiled and executed) to perform the functions described herein. In some implementations, the memory 1130 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0145] The processor 1140 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as in the memory 1130). In some specific implementations, the processor 1140 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be delivered to other systems or components of the device 1105, for example). For example, the processing system of the device 1105 may refer to a system including various other components or subcomponents of the device 1105, such as the processor 1140, or the transceiver 1115, or the communication manager 1120, or other components or combinations of components of the device 1105. The processing system of the device 1105 may interface with other components of the device 1105, and may process information (such as inputs or signals) received from other components, or output information to other components. For example, a chip or modem of the device 1105 may include a processing system and an interface for outputting information or for obtaining information or both. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1105 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1105 can obtain information or signal input, and the information can be passed to the processing system. A person of ordinary skill in the art will readily appreciate that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0146] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a UE. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving a DCI message, the DCI message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a TA command. The communication manager 1120 may be configured to or otherwise support a component for sending an uplink message associated with a TA command indicated in the DCI message to the network entity.

[0147] In some implementations, the communication manager 1120 may be configured to use or otherwise cooperate with the transceiver 1115, one or more antennas 1125, or any combination thereof to perform various operations (such as receiving, monitoring, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions that are executable by the processor 1140 to cause the device 1105 to perform various aspects of the dynamic TA indication in the DCI as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0148] Fig.12 A diagram of a system 1200 is shown that includes a device 1205 that supports dynamic TA indication in a DCI. The device 1205 may communicate with one or more network entities (such as one or more components of one or more BSs 140), one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (such as operatively, communicatively, functionally, electronically, electrically) via one or more buses (such as a bus 1240).

[0149] As described herein, the transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both. In some implementations, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some implementations, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some implementations, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (such as concurrently). The transceiver 1210 may also include a modem for modulating a signal, providing the modulated signal for transmission (such as through one or more antennas 1215, through a wired transmitter), receiving the modulated signal (such as from one or more antennas 1215, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations associated with received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (such as a processor 1235 or a memory 1225 or both) may be included in a chip or chip component installed in the device 1205. In some implementations, the transceiver may be operable to support communications via one or more communication links, such as communication link 125 , backhaul communication link 120 , midhaul communication link 162 , and fronthaul communication link 168 .

[0150] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code 1230 may not be directly executable by the processor 1235, but may cause a computer (such as when compiled and executed) to perform the functions described herein. In one implementation, the memory 1225 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0151] The processor 1235 may include an intelligent hardware device (such as a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some specific implementations, the processor 1235 may be configured to operate a memory array using a memory controller. In some specific implementations, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (such as a memory 1225) to enable the device 1205 to perform various functions (such as functions or tasks that support dynamic TA indications in DCI). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform various functions described herein. The processor 1235 may be an example of a cloud computing platform (such as one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (such as by executing code 1230) to perform the functions of the device 1205. The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as in the memory 1225). In some specific implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be delivered to other systems or components of the device 1205, for example). For example, the processing system of the device 1205 may refer to a system including various other components or subcomponents of the device 1205, such as the processor 1235, or the transceiver 1210, or the communication manager 1220, or other components or combinations of components of the device 1205. The processing system of the device 1205 may interface with other components of the device 1205, and may process information (such as input or signals) received from other components, or output information to other components. For example, a chip or modem of the device 1205 may include a processing system and an interface for outputting information or for obtaining information or both. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1205 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1205 can obtain information or signal input, and the information can be passed to the processing system.Those of ordinary skill in the art will readily appreciate that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0152] In some implementations, the bus 1240 may support communications of a protocol layer of a protocol stack (such as within a protocol layer). In some implementations, the bus 1240 may support communications associated with a logical channel of a protocol stack (such as between protocol layers of a protocol stack), which may include communications performed within a component of the device 1205, or communications performed between different components of the device 1205 that may be co-located or located in different locations (such as, where the device 1205 may refer to a system in which one or more of the communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of these different components or divided between different components).

[0153] In some implementations, the communication manager 1220 can manage aspects of communications with the core network 130, such as via one or more wired or wireless backhaul links. For example, the communication manager 1220 can manage the sending of data communications for client devices, such as one or more UEs 115. In some implementations, the communication manager 1220 can manage communications with other network entities 105, and can include a controller or scheduler for controlling communications with the UE 115 in collaboration with the other network entities 105. In some implementations, the communication manager 1220 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0154] According to examples as disclosed herein, the communication manager 1220 may support wireless communication at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a component for sending a DCI message to a UE, the DCI message including one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a TA command. The communication manager 1220 may be configured to or otherwise support a component for receiving an uplink message associated with a TA command indicated in the DCI message from the UE.

[0155] In some implementations, the communication manager 1220 may be configured to perform various operations (such as receiving, obtaining, monitoring, outputting, transmitting) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (such as where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions that are executable by the processor 1235 to cause the device 1205 to perform various aspects of the dynamic TA indication in the DCI as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0156] Fig.13 1 is a flowchart illustrating a method 1300 for supporting dynamic TA indication in DCI. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The UE 115 described herein performs. In some implementations, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0157] At 1305, the method may include receiving a DCI message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format including a CRC scrambled by a CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a TA command. The operations of 1305 may be performed according to examples as disclosed herein.

[0158] At 1310, the method may include sending an uplink message associated with the TA command indicated in the DCI message to a network entity. The operations of 1310 may be performed according to examples as disclosed herein.

[0159] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting dynamic TA indication in DCI. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 and Fig.12In some implementations, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0160] At 1405, the method may include sending a DCI message to the UE, the DCI message including one or more fields associated with scheduling information for communication between a network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format including a CRC scrambled by the CS-RNTI, the one or more fields being populated with a value indicating that the DCI message includes a TA command. The operations of 1405 may be performed according to examples as disclosed herein.

[0161] At 1410, the method may include receiving an uplink message associated with a TA command indicated in a DCI message from a UE. The operations of 1410 may be performed according to examples as disclosed herein.

[0162] The following provides an overview of some aspects of the disclosure:

[0163] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a DCI message, the DCI message comprising one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0164] Aspect 2: A method according to aspect 1, wherein receiving the DCI message comprises: receiving an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0165] Aspect 3: The method according to aspect 1, wherein receiving the DCI message comprises: receiving a downlink DCI message, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0166] Aspect 4: A method according to any one of Aspects 1 to 3, wherein sending the uplink message associated with the timing advance command also includes: applying the timing advance command to the uplink message, and the uplink message is scheduled on one CC of one or more CCs associated with a TAG identifier (TAG-ID) included in the timing advance command.

[0167] Aspect 5: A method according to Aspect 4, wherein each of the one or more CCs is associated with a single timing advance command, and the method further includes: applying the timing advance command to the uplink message in one of the one or more CCs, and the one of the one or more CCs is associated with the TAG-ID included in the timing advance command.

[0168] Aspect 6: A method according to Aspect 4, wherein each of the one or more CCs is associated with multiple different timing advance commands with corresponding different TAG-IDs, and the method further includes: applying the timing advance command to the uplink message in one of the one or more CCs, the uplink message in one of the one or more CCs is associated with a CORESET pool index, and the CORESET pool index is also associated with the TAG-ID included in the timing advance command.

[0169] Aspect 7: A method according to Aspect 4, wherein each of the one or more CCs is associated with multiple different timing advance commands each associated with the TAG-ID, and the method further includes: applying the timing advance command to the uplink message in the one or more CCs, and the uplink message in the one or more CCs is associated with the CORESET pool index in which the DCI message is received.

[0170] Aspect 8: A method according to any one of Aspects 1 to 3, wherein sending the uplink message associated with the timing advance command also includes: applying the timing advance command to the uplink message scheduled in one CC among one or more CCs, and selecting the one component carrier among the one or more component carriers based on whether the CIF exists in the DCI message.

[0171] Aspect 9: The method according to aspect 8, wherein the CIF is present in the DCI message, and the one CC among the one or more CCs is associated with a TAG-ID associated with the CC indicated by the CIF.

[0172] Aspect 10: The method according to aspect 8, wherein the CIF is not present in the DCI message, and the one CC among the one or more CCs is associated with a TAG-ID associated with a default CC.

[0173] Aspect 11: The method according to aspect 10, wherein the default CC is an uplink CC associated with the downlink CC in which the DCI message is received.

[0174] Aspect 12: The method according to aspect 8, wherein the uplink message in one CC of the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is received.

[0175] Aspect 13: A method according to any one of Aspects 1 to 12, wherein receiving the DCI message includes: receiving the DCI message in one or more symbols of a DCI reception time slot, wherein the timing advance command is applicable to a determined number of time slots after a specified time slot associated with the DCI reception time slot, and the determined number of time slots is based on the SPS PDSCH release processing capability of the UE.

[0176] Aspect 14: The method according to aspect 13, wherein the designated time slot is the last time slot in a set of multiple uplink time slots overlapping with the DCI reception time slot.

[0177] Aspect 15: The method according to aspect 13, wherein the designated time slot is the last time slot in a set of multiple uplink time slots that overlap with the one or more symbols of the DCI reception time slot.

[0178] Aspect 16: A method according to any one of Aspects 1 to 15, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index, and wherein sending the uplink message associated with the timing advance command indicated in the DCI message further comprises: sending the uplink message using timing advance, wherein the timing advance is based on a previous timing advance value associated with the CORESET pool index and the timing advance adjustment index value.

[0179] Aspect 17: The method according to aspect 16, wherein the CORESET pool index is the same as the CORESET pool index in which the DCI message is received.

[0180] Aspect 18: The method according to aspect 16, wherein the CORESET pool index is the same as the CORESET pool index associated with the TAG-ID included in the DCI message.

[0181] Aspect 19: A method according to any one of Aspects 1 to 15, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index, wherein sending the uplink message associated with the timing advance command indicated in the DCI message also includes: sending the uplink message using a timing advance, wherein the timing advance is based on a previous timing advance value associated with the first CORESET pool index, the timing advance adjustment value associated with the reference CORESET pool index, and the timing advance adjustment offset value associated with the first CORESET pool index.

[0182] Aspect 20: The method according to aspect 19 further comprises: receiving an indication of the reference CORESET pool index.

[0183] Aspect 21: A method according to any one of Aspects 1 to 15, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index, wherein sending the uplink message associated with the timing advance command indicated in the DCI message also includes: sending the uplink message using a timing advance, wherein the timing advance is based on a current timing advance value associated with the reference CORESET pool index and the timing advance offset value associated with the first CORESET pool index.

[0184] Aspect 22: According to the method of aspect 21, the method also includes: receiving an indication of the reference CORESET pool index.

[0185] Aspect 23: A method according to any one of Aspects 1 to 22, wherein the one or more fields filled with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0186] Aspect 24: A method according to any one of Aspects 1 to 23, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0187] Aspect 25: The method according to any one of aspects 1 to 24, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0188] Aspect 26: The method according to any one of aspects 1 to 24, wherein the timing advance command indicates an absolute timing advance.

[0189] Aspect 27: A method according to any one of Aspects 1 to 26, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0190] Aspect 28: A method for performing wireless communications at a network entity, the method comprising: sending a DCI message to a UE, the DCI message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and receiving an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0191] Aspect 29: A method according to Aspect 28, wherein sending the DCI message comprises: sending an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0192] Aspect 30: A method according to aspect 28, wherein sending the DCI message includes: sending a downlink DCI message, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0193] Aspect 31: A method according to any one of Aspects 28 to 30, wherein receiving the uplink message further comprises: receiving the uplink message via one or more CCs, the one or more CCs being associated with the TAG-ID included in the timing advance command.

[0194] Aspect 32: A method according to any one of Aspects 28 to 30, wherein receiving the uplink message further comprises: receiving the uplink message via one CC among one or more CCs, and selecting the one component carrier among the one or more component carriers based on whether a CIF exists in the DCI message.

[0195] Aspect 33: The method according to aspect 32, wherein the CIF is present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with the CC indicated by the CIF.

[0196] Aspect 34: The method according to aspect 32, wherein the CIF is not present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with a default CC.

[0197] Aspect 35: The method according to aspect 34, wherein the default CC is an uplink CC associated with the downlink CC in which the DCI message is sent.

[0198] Aspect 36: The method according to aspect 32, wherein the uplink message in the one or more CCs is associated with a CORESET pool index of the CORESET in which the DCI message is sent.

[0199] Aspect 37: A method according to any one of aspects 28 to 36, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index.

[0200] Aspect 38: The method according to any one of aspects 28 to 37, wherein the CORESET pool index associated with the timing advance command is the same as the CORESET pool index in which the DCI message is sent.

[0201] Aspect 39: A method according to any one of aspects 28 to 37, wherein a CORESET pool index associated with the timing advance command and a CORESET pool index associated with a TAG-ID included in the DCI message are the same.

[0202] Aspect 40: A method according to any one of aspects 28 to 37, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index.

[0203] Aspect 41: According to the method of aspect 40, the method also includes: sending an indication of the reference CORESET pool index.

[0204] Aspect 42: A method according to any one of aspects 28 to 37, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index.

[0205] Aspect 43: According to the method of aspect 42, the method also includes: sending an indication of the reference CORESET pool index.

[0206] Aspect 44: A method according to any one of Aspects 28 to 43, wherein the one or more fields filled with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0207] Aspect 45: A method according to any one of Aspects 28 to 44, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0208] Aspect 46: A method according to any one of aspects 28 to 45, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0209] Aspect 47: A method according to any one of aspects 28 to 45, wherein the timing advance command indicates an absolute timing advance.

[0210] Aspect 48: A method according to any one of Aspects 28 to 47, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0211] Aspect 49: A device for performing wireless communications at a UE, the device comprising: one or more interfaces, the one or more interfaces being configured to: obtain a DCI message, the DCI message comprising one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and output to the network entity an uplink message associated with the timing advance command indicated in the DCI message.

[0212] Aspect 50: An apparatus according to Aspect 49, wherein in order to obtain the DCI message, the one or more interfaces are further configured to: obtain an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0213] Aspect 51: An apparatus according to Aspect 49, wherein in order to obtain the DCI message, the one or more interfaces are further configured to: obtain a downlink DCI message, wherein the downlink DCI message indicates the timing advance command, rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0214] Aspect 52: An apparatus according to any one of Aspects 49 to 51, wherein in order to output the uplink message associated with the timing advance command, the one or more interfaces are further configured to: apply the timing advance command to the uplink message, and the uplink message is scheduled on one CC of one or more CCs associated with the TAG-ID included in the timing advance command.

[0215] Aspect 53: An apparatus according to Aspect 52, wherein each of the one or more CCs is associated with a single timing advance command, and wherein the one or more interfaces are further configured to: apply the timing advance command to the uplink message in one of the one or more CCs, and the one of the one or more CCs is associated with the TAG-ID included in the timing advance command.

[0216] Aspect 54: An apparatus according to Aspect 52, wherein each of the one or more CCs is associated with multiple different timing advance commands having corresponding different TAG-IDs, and the one or more interfaces are further configured to: apply the timing advance command to the uplink message in one of the one or more CCs, the uplink message in one of the one or more CCs being associated with a CORESET pool index, and the CORESET pool index being also associated with the TAG-ID included in the timing advance command.

[0217] Aspect 55: An apparatus according to Aspect 52, wherein each of the one or more CCs is associated with multiple different timing advance commands each associated with the TAG-ID, and the one or more interfaces are further configured to: apply the timing advance command to the uplink message in the one or more CCs, and the uplink message in the one or more CCs is associated with the CORESET pool index in which the DCI message is obtained.

[0218] Aspect 56: An apparatus according to any one of Aspects 49 to 51, wherein in order to output the uplink message associated with the timing advance command, the one or more interfaces are further configured to: apply the timing advance command to the uplink message scheduled in one CC among one or more CCs, and select the one component carrier among the one or more component carriers based on whether the CIF is present in the DCI message.

[0219] Aspect 57: The apparatus according to Aspect 56, wherein the CIF is present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with the CC indicated by the CIF.

[0220] Aspect 58: The apparatus according to aspect 56, wherein the CIF is not present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with a default CC.

[0221] Aspect 59: The apparatus of aspect 58, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message was obtained.

[0222] Aspect 60: An apparatus according to any one of aspects 56 to 59, wherein the uplink message in one CC of the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message was obtained.

[0223] Aspect 61: An apparatus according to any one of Aspects 49 to 60, wherein in order to obtain the DCI message, the one or more interfaces are further configured to: obtain the DCI message in one or more symbols of the DCI reception time slot, wherein the timing advance command is applicable to a determined number of time slots after a specified time slot associated with the DCI reception time slot, and the determined number of time slots is based on the SPS PDSCH release processing capability of the UE.

[0224] Aspect 62: The apparatus of aspect 61, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with the DCI reception time slot.

[0225] Aspect 63: The apparatus according to aspect 61, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with one or more symbols of the DCI reception time slot.

[0226] Aspect 64: An apparatus according to any one of Aspects 49 to 63, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index, and wherein in order to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: output the uplink message using the timing advance, and the timing advance is based on a previous timing advance value associated with the CORESET pool index and the timing advance adjustment index value.

[0227] Aspect 65: The apparatus of aspect 64, wherein the CORESET pool index is the same as the CORESET pool index in which the DCI message is obtained.

[0228] Aspect 66: The apparatus of aspect 64, wherein the CORESET pool index is the same as a CORESET pool index associated with a TAG-ID included in the DCI message.

[0229] Aspect 67: An apparatus according to any one of Aspects 49 to 63, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index, wherein in order to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: output the uplink message using a timing advance, wherein the timing advance is based on a previous timing advance value associated with the first CORESET pool index, the timing advance adjustment value associated with the reference CORESET pool index, and the timing advance adjustment offset value associated with the first CORESET pool index.

[0230] Aspect 68: The apparatus according to aspect 67, wherein the one or more interfaces are further configured to: obtain an indication of the reference CORESET pool index.

[0231] Aspect 69: An apparatus according to any one of Aspects 49 to 63, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index, wherein in order to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: output the uplink message using a timing advance, wherein the timing advance is based on a current timing advance value associated with the reference CORESET pool index and the timing advance offset value associated with the first CORESET pool index.

[0232] Aspect 70: The apparatus according to aspect 69, wherein the one or more interfaces are further configured to: obtain an indication of the reference CORESET pool index.

[0233] Aspect 71: An apparatus according to any one of Aspects 49 to 70, wherein the one or more fields filled with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0234] Aspect 72: An apparatus according to any one of Aspects 49 to 71, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0235] Aspect 73: An apparatus according to any one of aspects 49 to 72, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0236] Aspect 74: An apparatus according to any one of aspects 49 to 72, wherein the timing advance command indicates an absolute timing advance.

[0237] Aspect 75: An apparatus according to any one of Aspects 49 to 74, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0238] Aspect 76: A device for performing wireless communications at a network entity, the device comprising: one or more interfaces, the one or more interfaces being configured to: output a DCI message to a UE, the DCI message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is output in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and obtain from the UE an uplink message associated with the timing advance command indicated in the DCI message.

[0239] Aspect 77: An apparatus according to Aspect 76, wherein in order to output the DCI message, the one or more interfaces are further configured to: output an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0240] Aspect 78: An apparatus according to Aspect 76, wherein in order to output the DCI message, the one or more interfaces are further configured to: output a downlink DCI message, wherein the downlink DCI message indicates the timing advance command, rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0241] Aspect 79: An apparatus according to any one of Aspects 76 to 78, wherein in order to obtain the uplink message, the one or more interfaces are further configured to: obtain the uplink message via one or more CCs, and the one or more CCs are associated with the TAG-ID included in the timing advance command.

[0242] Aspect 80: An apparatus according to any one of Aspects 76 to 78, wherein in order to obtain the uplink message, the one or more interfaces are further configured to: obtain the uplink message via one CC among one or more CCs, and select the one component carrier among the one or more component carriers based on whether the CIF exists in the DCI message.

[0243] Aspect 81: The apparatus according to aspect 80, wherein the CIF is present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with the CC indicated by the CIF.

[0244] Aspect 82: The apparatus according to aspect 80, wherein the CIF is not present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with a default CC.

[0245] Aspect 83: The apparatus of aspect 82, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message is output.

[0246] Aspect 84: The apparatus of aspect 80, wherein the uplink message in the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is output.

[0247] Aspect 85: An apparatus according to any one of aspects 76 to 84, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index.

[0248] Aspect 86: An apparatus according to any one of Aspects 76 to 85, wherein a CORESET pool index associated with the timing advance command is the same as a CORESET pool index in which the DCI message is output.

[0249] Aspect 87: An apparatus according to any one of Aspects 76 to 85, wherein a CORESET pool index associated with the timing advance command and a CORESET pool index associated with a TAG-ID included in the DCI message are the same.

[0250] Aspect 88: An apparatus according to any one of aspects 76 to 85, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index.

[0251] Aspect 89: The apparatus according to aspect 88, wherein the one or more interfaces are further configured to: output an indication of the reference CORESET pool index.

[0252] Aspect 90: An apparatus according to any one of aspects 76 to 85, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index.

[0253] Aspect 91: According to the apparatus of Aspect 90, the one or more interfaces are further configured to: output an indication of the reference CORESET pool index.

[0254] Aspect 92: An apparatus according to any one of Aspects 76 to 91, wherein the one or more fields filled with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0255] Aspect 93: An apparatus according to any one of Aspects 76 to 92, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0256] Aspect 94: An apparatus according to any one of aspects 76 to 93, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0257] Aspect 95: An apparatus according to any one of aspects 76 to 93, wherein the timing advance command indicates an absolute timing advance.

[0258] Aspect 96: An apparatus according to any one of Aspects 76 to 95, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0259] Aspect 97: An apparatus for performing wireless communications at a UE, the apparatus comprising: a component for receiving a DCI message, the DCI message comprising one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and a component for sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0260] Aspect 98: An apparatus according to Aspect 97, wherein the component for receiving the DCI message includes: a component for receiving an uplink DCI message, wherein the uplink DCI message indicates the timing advance command rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0261] Aspect 99: An apparatus according to Aspect 97, wherein the component for receiving the DCI message includes: a component for receiving a downlink DCI message, wherein the downlink DCI message indicates the timing advance command rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0262] Aspect 100: An apparatus according to any one of Aspects 97 to 99, wherein the component for sending the uplink message associated with the timing advance command also includes: a component for applying the timing advance command to the uplink message, and the uplink message is scheduled on one of one or more CCs associated with the TAG-ID included in the timing advance command.

[0263] Aspect 101: An apparatus according to Aspect 100, wherein each of the one or more CCs is associated with a single timing advance command, and the apparatus further comprises: a component for applying the timing advance command to the uplink message in one of the one or more CCs, the one of the one or more CCs being associated with the TAG-ID included in the timing advance command.

[0264] Aspect 102: An apparatus according to Aspect 100, wherein each of the one or more CCs is associated with multiple different timing advance commands having corresponding different TAG-IDs, and the apparatus further includes: a component for applying the timing advance command to the uplink message in one of the one or more CCs, the uplink message in one of the one or more CCs being associated with a CORESET pool index, and the CORESET pool index being also associated with the TAG-ID included in the timing advance command.

[0265] Aspect 103: An apparatus according to Aspect 100, wherein each of the one or more CCs is associated with a plurality of different timing advance commands each associated with the TAG-ID, and the apparatus further comprises: a component for applying the timing advance command to the uplink message in the one or more CCs, the uplink message in the one or more CCs being associated with a CORESET pool index in which the DCI message is received.

[0266] Aspect 104: An apparatus according to any one of Aspects 97 to 99, wherein the component for sending the uplink message associated with the timing advance command also includes: a component for applying the timing advance command to the uplink message scheduled in one CC among one or more CCs, and selecting the one of the one or more component carriers based on whether a CIF is present in the DCI message.

[0267] Aspect 105: The apparatus according to Aspect 104, wherein the CIF is present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with the CC indicated by the CIF.

[0268] Aspect 106: The apparatus according to aspect 104, wherein the CIF is not present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with a default CC.

[0269] Aspect 107: The apparatus of aspect 106, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message is received.

[0270] Aspect 108: The apparatus of aspect 104, wherein the uplink message in a CC of the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is received.

[0271] Aspect 109: An apparatus according to any one of Aspects 97 to 108, wherein the component for receiving the DCI message includes: a component for receiving the DCI message in one or more symbols of a DCI reception time slot, wherein the timing advance command is applicable to a determined number of time slots after a specified time slot associated with the DCI reception time slot, and the determined number of time slots is based on the SPS PDSCH release processing capability of the UE.

[0272] Aspect 110: The apparatus of aspect 109, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with the DCI reception time slot.

[0273] Aspect 111: The apparatus of aspect 109, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with one or more symbols of the DCI reception time slot.

[0274] Aspect 112: An apparatus according to any one of Aspects 97 to 111, wherein the component for sending the uplink message associated with the timing advance command indicated in the DCI message also includes: a component for sending the uplink message using a timing advance, wherein the timing advance is based on a previous timing advance value associated with the CORESET pool index and the timing advance adjustment index value.

[0275] Aspect 113: The apparatus of aspect 112, wherein the CORESET pool index is the same as a CORESET pool index in which the DCI message is received.

[0276] Aspect 114: The apparatus of aspect 112, wherein the CORESET pool index is the same as a CORESET pool index associated with a TAG-ID included in the DCI message.

[0277] Aspect 115: An apparatus according to any one of Aspects 97 to 111, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index, wherein the component for sending the uplink message associated with the timing advance command indicated in the DCI message also includes: a component for sending the uplink message using a timing advance, wherein the timing advance is based on a previous timing advance value associated with the first CORESET pool index, the timing advance adjustment value associated with the reference CORESET pool index, and the timing advance adjustment offset value associated with the first CORESET pool index.

[0278] Aspect 116: The apparatus according to Aspect 115, further comprising: means for receiving an indication of the reference CORESET pool index.

[0279] Aspect 117: An apparatus according to any one of Aspects 97 to 111, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index, wherein the component for sending the uplink message associated with the timing advance command indicated in the DCI message also includes: a component for sending the uplink message using a timing advance, wherein the timing advance is based on a current timing advance value associated with the reference CORESET pool index and the timing advance offset value associated with the first CORESET pool index.

[0280] Aspect 118: The apparatus according to Aspect 117, further comprising: means for receiving an indication of the reference CORESET pool index.

[0281] Aspect 119: An apparatus according to any one of Aspects 97 to 118, wherein the one or more fields filled with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0282] Aspect 120: An apparatus according to any one of Aspects 97 to 119, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0283] Aspect 121: An apparatus according to any one of aspects 97 to 120, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0284] Aspect 122: An apparatus according to any one of aspects 97 to 120, wherein the timing advance command indicates an absolute timing advance.

[0285] Aspect 123: An apparatus according to any one of Aspects 97 to 122, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0286] Aspect 124: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a component for sending a DCI message to a UE, the DCI message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and a component for receiving an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0287] Aspect 125: An apparatus according to Aspect 124, wherein the component for sending the DCI message includes: a component for sending an uplink DCI message, wherein the uplink DCI message indicates the timing advance command rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0288] Aspect 126: An apparatus according to Aspect 124, wherein the component for sending the DCI message includes: a component for sending a downlink DCI message, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0289] Aspect 127: An apparatus according to any one of Aspects 124 to 126, wherein the component for receiving the uplink message also includes: a component for receiving the uplink message via one or more CCs, and the one or more CCs are associated with the TAG-ID included in the timing advance command.

[0290] Aspect 128: An apparatus according to any one of Aspects 124 to 126, wherein the component for receiving the uplink message also includes: a component for receiving the uplink message via one CC among one or more CCs, and selecting the one of the one or more component carriers based on whether a CIF is present in the DCI message.

[0291] Aspect 129: The apparatus according to Aspect 128, wherein the CIF is present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with the CC indicated by the CIF.

[0292] Aspect 130: The apparatus according to aspect 128, wherein the CIF is not present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with a default CC.

[0293] Aspect 131: The apparatus of aspect 130, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message is sent.

[0294] Aspect 132: The apparatus of aspect 128, wherein the uplink message in the one or more CCs is associated with a CORESET pool index of the CORESET in which the DCI message is sent.

[0295] Aspect 133: An apparatus according to any one of aspects 124 to 132, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index.

[0296] Aspect 134: An apparatus according to any one of Aspects 124 to 133, wherein a CORESET pool index associated with the timing advance command is the same as a CORESET pool index in which the DCI message is sent.

[0297] Aspect 135: An apparatus according to any one of Aspects 124 to 133, wherein a CORESET pool index associated with the timing advance command and a CORESET pool index associated with a TAG-ID included in the DCI message are the same.

[0298] Aspect 136: An apparatus according to any one of aspects 124 to 133, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index.

[0299] Aspect 137: The apparatus according to Aspect 136, further comprising: a means for sending an indication of the reference CORESET pool index.

[0300] Aspect 138: An apparatus according to any one of aspects 124 to 133, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index.

[0301] Aspect 139: The apparatus according to Aspect 138, further comprising: a component for sending an indication of the reference CORESET pool index.

[0302] Aspect 140: An apparatus according to any one of Aspects 124 to 139, wherein the one or more fields populated with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0303] Aspect 141: An apparatus according to any one of Aspects 124 to 140, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0304] Aspect 142: An apparatus according to any one of aspects 124 to 141, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0305] Aspect 143: An apparatus according to any one of aspects 124 to 141, wherein the timing advance command indicates an absolute timing advance.

[0306] Aspect 144: An apparatus according to any one of Aspects 124 to 143, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0307] Aspect 145: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the following operations: receiving a DCI message, the DCI message comprising one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and sending an uplink message associated with the timing advance command indicated in the DCI message to the network entity.

[0308] Aspect 146: A non-transitory computer-readable medium according to Aspect 145, wherein the instructions for receiving the DCI message are executable by the processor to: receive an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0309] Aspect 147: A non-transitory computer-readable medium according to Aspect 145, wherein the instructions for receiving the DCI message are capable of being executed by the processor to: receive a downlink DCI message, wherein the downlink DCI message indicates the timing advance command, rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0310] Aspect 148: A non-transitory computer-readable medium according to Aspects 145 to 147, wherein the instructions for sending the uplink message associated with the timing advance command are capable of being further executed by the processor to: apply the timing advance command to the uplink message, and the uplink message is scheduled on one of one or more CCs associated with the TAG-ID included in the timing advance command.

[0311] Aspect 149: A non-transitory computer-readable medium according to Aspect 148, wherein each of the one or more CCs is associated with a single timing advance command, and the instruction is capable of being further executed by the processor to: apply the timing advance command to the uplink message in one of the one or more CCs, and the one of the one or more CCs is associated with the TAG-ID included in the timing advance command.

[0312] Aspect 150: A non-transitory computer-readable medium according to Aspect 148, wherein each of the one or more CCs is associated with multiple different timing advance commands having corresponding different TAG-IDs, and the instructions are capable of being further executed by the processor to: apply the timing advance command to the uplink message in one of the one or more CCs, the uplink message in one of the one or more CCs being associated with a CORESET pool index, and the CORESET pool index is also associated with the TAG-ID included in the timing advance command.

[0313] Aspect 151: A non-transitory computer-readable medium according to Aspect 148, wherein each of the one or more CCs is associated with a plurality of different timing advance commands each associated with the TAG-ID, and the instructions are capable of being further executed by the processor to: apply the timing advance command to the uplink message in the one or more CCs, the uplink message in the one or more CCs being associated with a CORESET pool index in which the DCI message is received.

[0314] Aspect 152: A non-transitory computer-readable medium according to Aspects 145 to 147, wherein the instructions for sending the uplink message associated with the timing advance command are capable of being further executed by the processor to: apply the timing advance command to the uplink message scheduled in one CC among one or more CCs, and select the one of the one or more component carriers based on whether the CIF is present in the DCI message.

[0315] Aspect 153: The non-transitory computer-readable medium according to aspect 152, wherein the CIF is present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with the CC indicated by the CIF.

[0316] Aspect 154: The non-transitory computer-readable medium of aspect 152, wherein the CIF is not present in the DCI message, and the one CC of the one or more CCs is associated with a TAG-ID associated with a default CC.

[0317] Aspect 155: The non-transitory computer-readable medium of aspect 154, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message is received.

[0318] Aspect 156: The non-transitory computer-readable medium of aspect 152, wherein the uplink message in one CC of the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is received.

[0319] Aspect 157: A non-transitory computer-readable medium according to any one of Aspects 145 to 156, wherein the instructions for receiving the DCI message are executable by the processor to: receive the DCI message in one or more symbols of a DCI reception time slot, wherein the timing advance command is applicable to a determined number of time slots after a specified time slot associated with the DCI reception time slot, and the determined number of time slots is based on the SPS PDSCH release processing capability of the UE.

[0320] Aspect 158: The non-transitory computer-readable medium of aspect 157, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with the DCI reception time slot.

[0321] Aspect 159: The non-transitory computer-readable medium of aspect 157, wherein the designated time slot is a last time slot in a set of multiple uplink time slots that overlap with one or more symbols of the DCI reception time slot.

[0322] Aspect 160: A non-transitory computer-readable medium according to any one of Aspects 145 to 159, wherein the instructions for sending the uplink message associated with the timing advance command indicated in the DCI message are capable of being further executed by the processor to: send the uplink message using a timing advance, wherein the timing advance is based on a previous timing advance value associated with the CORESET pool index and the timing advance adjustment index value.

[0323] Aspect 161: The non-transitory computer-readable medium of aspect 160, wherein the CORESET pool index is the same as a CORESET pool index in which the DCI message is received.

[0324] Aspect 162: The non-transitory computer-readable medium of aspect 160, wherein the CORESET pool index is the same as a CORESET pool index associated with a TAG-ID included in the DCI message.

[0325] Aspect 163: A non-transitory computer-readable medium according to any one of Aspects 145 to 159, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index, wherein the instructions for sending the uplink message associated with the timing advance command indicated in the DCI message are further executable by the processor to: send the uplink message using a timing advance, the timing advance being based on a previous timing advance value associated with the first CORESET pool index, the timing advance adjustment value associated with the reference CORESET pool index, and the timing advance adjustment offset value associated with the first CORESET pool index.

[0326] Aspect 164: The non-transitory computer-readable medium of aspect 163, wherein the instructions are further executable by the processor to: receive an indication of the reference CORESET pool index.

[0327] Aspect 165: A non-transitory computer-readable medium according to any one of Aspects 145 to 159, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index, wherein the instructions for sending the uplink message associated with the timing advance command indicated in the DCI message are further executable by the processor to: send the uplink message using a timing advance, the timing advance being based on a current timing advance value associated with the reference CORESET pool index and the timing advance offset value associated with the first CORESET pool index.

[0328] Aspect 166: The non-transitory computer-readable medium of aspect 165, wherein the instructions are further executable by the processor to: receive an indication of the reference CORESET pool index.

[0329] Aspect 167: A non-transitory computer-readable medium according to any one of Aspects 145 to 166, wherein the one or more fields populated with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0330] Aspect 168: A non-transitory computer-readable medium according to any one of Aspects 145 to 167, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0331] Aspect 169: The non-transitory computer readable medium of any one of aspects 145 to 168, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0332] Aspect 170: The non-transitory computer-readable medium of any one of aspects 145 to 168, wherein the timing advance command indicates an absolute timing advance.

[0333] Aspect 171: A non-transitory computer-readable medium according to any one of Aspects 145 to 170, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0334] Aspect 172: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the following operations: sending a DCI message to a UE, the DCI message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format comprising a CRC scrambled by a CS-RNTI, the one or more fields being filled with values ​​indicating that the DCI message includes a timing advance command; and receiving an uplink message associated with the timing advance command indicated in the DCI message from the UE.

[0335] Aspect 173: A non-transitory computer-readable medium according to Aspect 172, wherein the instructions for sending the DCI message are executable by the processor to: send an uplink DCI message, wherein the uplink DCI message indicates the timing advance command, rather than scheduling an uplink shared channel message or activating or releasing a CG configuration.

[0336] Aspect 174: A non-transitory computer-readable medium according to Aspect 172, wherein the instructions for sending the DCI message are capable of being executed by the processor to: send a downlink DCI message, wherein the downlink DCI message indicates the timing advance command, rather than scheduling a downlink shared channel message or activating or releasing an SPS configuration.

[0337] Aspect 175: A non-transitory computer-readable medium according to any one of Aspects 172 to 174, wherein the instructions for receiving the uplink message are capable of being further executed by the processor to: receive the uplink message via one or more CCs, wherein the one or more CCs are associated with the TAG-ID included in the timing advance command.

[0338] Aspect 176: A non-transitory computer-readable medium according to any one of Aspects 172 to 174, wherein the instructions for receiving the uplink message are capable of being further executed by the processor to: receive the uplink message via one CC among one or more CCs, and select the one of the one or more component carriers based on whether the CIF is present in the DCI message.

[0339] Aspect 177: The non-transitory computer-readable medium according to aspect 176, wherein the CIF is present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with the CC indicated by the CIF.

[0340] Aspect 178: The non-transitory computer-readable medium according to aspect 176, wherein the CIF is not present in the DCI message, and the one or more CCs are associated with a TAG-ID associated with a default CC.

[0341] Aspect 179: The non-transitory computer-readable medium of aspect 178, wherein the default CC is an uplink CC associated with a downlink CC in which the DCI message is sent.

[0342] Aspect 180: The non-transitory computer-readable medium of aspect 176, wherein the uplink message in the one or more CCs is associated with a CORESET pool index of a CORESET in which the DCI message is sent.

[0343] Aspect 181: The non-transitory computer-readable medium of any one of aspects 172 to 180, wherein the timing advance command is a timing advance adjustment index value associated with a CORESET pool index.

[0344] Aspect 182: The non-transitory computer-readable medium of any one of Aspects 172 to 181, wherein a CORESET pool index associated with the timing advance command is the same as a CORESET pool index in which the DCI message is sent.

[0345] Aspect 183: A non-transitory computer-readable medium according to any one of Aspects 172 to 181, wherein a CORESET pool index associated with the timing advance command and a CORESET pool index associated with a TAG-ID included in the DCI message are the same.

[0346] Aspect 184: A non-transitory computer-readable medium according to any one of Aspects 172 to 181, wherein the timing advance command is a timing advance adjustment offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index.

[0347] Aspect 185: The non-transitory computer-readable medium of aspect 184, wherein the instructions are further executable by the processor to: send an indication of the reference CORESET pool index.

[0348] Aspect 186: A non-transitory computer-readable medium according to any one of Aspects 172 to 181, wherein the timing advance command is a timing advance offset value associated with a first CORESET pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index.

[0349] Aspect 187: The non-transitory computer-readable medium of aspect 186, wherein the instructions are further executable by the processor to: send an indication of the reference CORESET pool index.

[0350] Aspect 188: A non-transitory computer-readable medium according to any one of Aspects 172 to 187, wherein the one or more fields populated with the value indicating that the DCI message includes the timing advance command include at least one of an RV field, an MCS field, an NDI field, an FDRA field, or an HPN field.

[0351] Aspect 189: A non-transitory computer-readable medium according to any one of Aspects 172 to 188, wherein the timing advance command is indicated in at least one of a TDRA field, an HPN field, a frequency hopping flag field, a TPC field, a PUCCH resource indicator field, or a PDSCH to HARQ feedback timing indicator field within the DCI message.

[0352] Aspect 190: The non-transitory computer readable medium of any one of aspects 172 to 189, wherein the timing advance command indicates a timing adjustment relative to a previous timing advance.

[0353] Aspect 191: The non-transitory computer-readable medium of any one of aspects 172 to 189, wherein the timing advance command indicates an absolute timing advance.

[0354] Aspect 192: A non-transitory computer-readable medium according to any one of Aspects 172 to 191, wherein the one or more fields of the DCI message filled with a value indicating that the DCI message includes the timing advance command are not filled with a value indicating the scheduling information for the communication between the UE and the network entity.

[0355] As used herein, the term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database, or other data structure), reasoning, ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data stored in a memory), etc. Additionally, "determining" may include resolving, selecting, choosing, establishing, and other such similar actions.

[0356] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc.

[0357] The various illustrative logical components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented using hardware or software depends on the specific application and design constraints imposed on the overall system.

[0358] The hardware and data processing apparatus for implementing the various illustrative logic pieces, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be performed by circuits specific to a given function.

[0359] In one or more aspects, the functions described may be implemented using hardware, digital electronic circuitry, computer software, firmware (including the structures disclosed in this specification and their structural equivalents), or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, such as one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device.

[0360] If implemented in software, these functions can be stored on a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. The process of the method or algorithm disclosed herein can be implemented in a processor executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any medium that can realize the transfer of a computer program from one location to another. The storage medium can be any available medium that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection can be appropriately referred to as a computer-readable medium. As used herein, disks and optical disks include compact disks (CDs), laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks. Disks can magnetically copy data, while optical disks can optically copy data with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0361] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the specific implementations shown herein, but should be granted the widest scope consistent with the disclosure, the principles and features disclosed herein.

[0362] Additionally, one of ordinary skill in the art will readily appreciate that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0363] Certain features described in this specification in the context of a single implementation may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in some combination and even initially claimed as such, one or more features from a claimed combination may be removed from the combination, and a claimed combination may involve subcombinations or variations of subcombinations.

[0364] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. Further, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted can be incorporated into the schematically illustrated example process. For example, one or more additional operations can be performed before, after, at the same time, or between any operations in the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of each system component in the specific implementation described above should not be understood as requiring such separation in all specific implementations, but it should be understood that the described program components and systems can usually be integrated together in a single software product, or be packaged in multiple software products. In addition, other specific implementations are within the scope of the following claims. In some specific implementations, the actions recited in the claims can be performed in different orders and still achieve the desired result.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more interfaces, the one or more interfaces being configured to: obtaining a downlink control information (DCI) message, the downlink control information (DCI) message comprising one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is obtained in a DCI format, the DCI format comprising a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; as well as An uplink message associated with the timing advance command indicated in the DCI message is output.

2. The apparatus according to claim 1, wherein in order to obtain the DCI message, the one or more interfaces are further configured to: An uplink DCI message is obtained, wherein the uplink DCI message indicates the timing advance command instead of a scheduling uplink shared channel message or a grant (CG) configuration that activates or releases a configuration.

3. The apparatus of claim 1 , wherein to obtain the DCI message, the one or more interfaces are further configured to: A downlink DCI message is obtained, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing a semi-persistent scheduling (SPS) configuration.

4. The apparatus of claim 1 , wherein to output the uplink message associated with the timing advance command, the one or more interfaces are further configured to: The timing advance command is applied to the uplink message, the uplink message being scheduled on one of one or more component carriers (CCs) associated with a timing advance group identifier (TAG-ID) included in the timing advance command.

5. The apparatus of claim 4, wherein each CC of the one or more CCs is associated with a single timing advance command, and wherein the one or more interfaces are further configured to: The timing advance command is applied to the uplink message in one of the one or more CCs, the one of the one or more CCs being associated with the TAG-ID included in the timing advance command.

6. The apparatus of claim 4, wherein each CC of the one or more CCs is associated with a plurality of different timing advance commands having corresponding different TAG-IDs, and the one or more interfaces are further configured to: The timing advance command is applied to the uplink message in one of the one or more CCs, wherein the uplink message in one of the one or more CCs is associated with a control resource set (CORESET) pool index, and the control resource set (CORESET) pool index is also associated with the TAG-ID included in the timing advance command.

7. The apparatus of claim 4, wherein each CC of the one or more CCs is associated with a plurality of different timing advance commands each associated with the TAG-ID, and the one or more interfaces are further configured to: The timing advance command is applied to the uplink message in the one or more CCs, the uplink message in the one or more CCs being associated with a control resource set (CORESET) pool index in which the DCI message is obtained.

8. The apparatus of claim 1 , wherein to output the uplink message associated with the timing advance command, the one or more interfaces are further configured to: The timing advance command is applied to the uplink message, the uplink message being scheduled in one of one or more component carriers (CCs), the one of the one or more component carriers being selected based at least in part on whether a carrier indicator field (CIF) is present in the DCI message.

9. The apparatus of claim 1 , wherein to obtain the DCI message, the one or more interfaces are further configured to: The DCI message is obtained in one or more symbols of a DCI reception time slot, wherein the timing advance command is applicable to a determined number of time slots after a specified time slot associated with the DCI reception time slot, and the determined number of time slots is at least partially based on a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) release processing capability of the UE.

10. The apparatus of claim 1 , wherein the timing advance command is a timing advance adjustment index value associated with a control resource set (CORESET) pool index, wherein to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: The uplink message is output using a timing advance that is based on a previous timing advance value associated with the CORESET pool index and the timing advance adjustment index value.

11. The apparatus of claim 10, wherein the CORESET pool index is the same as a CORESET pool index in which the DCI message is obtained.

12. The apparatus of claim 10, wherein the CORESET pool index is the same as a CORESET pool index associated with a timing group advance identifier (TAG-ID) included in the DCI message.

13. The apparatus of claim 1 , wherein the timing advance command is a timing advance adjustment offset value associated with a first control resource set (CORESET) pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index, wherein to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: The uplink message is output using a timing advance based on a previous timing advance value associated with the first CORESET pool index, the timing advance adjustment value associated with the reference CORESET pool index, and the timing advance adjustment offset value associated with the first CORESET pool index.

14. The apparatus of claim 1 , wherein the timing advance command is a timing advance offset value associated with a first control resource set (CORESET) pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index, wherein to output the uplink message associated with the timing advance command indicated in the DCI message, the one or more interfaces are further configured to: The uplink message is output using a timing advance based on a current timing advance value associated with the reference CORESET pool index and the timing advance offset value associated with the first CORESET pool index.

15. The apparatus of claim 1, wherein the one or more fields of the DCI message populated with a value indicating that the DCI message includes the timing advance command are not populated with a value indicating the scheduling information for the communication between the UE and the network entity.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more interfaces, the one or more interfaces being configured to: Outputting a downlink control information (DCI) message to a user equipment (UE), the downlink control information (DCI) message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is output in a DCI format, the DCI format comprising a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; as well as An uplink message associated with the timing advance command indicated in the DCI message is obtained from the UE.

17. The apparatus of claim 16, wherein to output the DCI message, the one or more interfaces are further configured to: An uplink DCI message is output, wherein the uplink DCI message indicates the timing advance command instead of a scheduling uplink shared channel message or a grant (CG) configuration that activates or releases a configuration.

18. The apparatus of claim 16, wherein to output the DCI message, the one or more interfaces are further configured to: A downlink DCI message is output, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing a semi-persistent scheduling (SPS) configuration.

19. The apparatus of claim 16, wherein to obtain the uplink message, the one or more interfaces are further configured to: The uplink message is obtained via one or more component carriers (CCs) associated with a timing advance group identifier (TAG-ID) included in the timing advance command.

20. The apparatus of claim 16, wherein to obtain the uplink message, the one or more interfaces are further configured to: The uplink message is obtained via one of one or more component carriers (CCs), the one of the one or more component carriers being selected based at least in part on whether a carrier indicator field (CIF) is present in the DCI message.

21. The apparatus of claim 16, wherein a control resource set (CORESET) pool index associated with the timing advance command and a CORESET pool index associated with a timing group advance identifier (TAG-ID) included in the DCI message are the same.

22. The apparatus of claim 16, wherein the timing advance command is a timing advance adjustment offset value associated with a first control resource set (CORESET) pool index and represents a timing advance offset relative to a timing advance adjustment value associated with a reference CORESET pool index.

23. The apparatus of claim 16, wherein the timing advance command is a timing advance offset value associated with a first control resource set (CORESET) pool index and represents a timing advance offset relative to a timing advance value associated with a reference CORESET pool index.

24. The apparatus of claim 16, wherein the one or more fields of the DCI message populated with a value indicating that the DCI message includes the timing advance command are not populated with a value indicating the scheduling information for the communication between the UE and the network entity.

25. A method for wireless communication at a user equipment (UE), the method comprising: receiving a downlink control information (DCI) message including one or more fields associated with scheduling information for communication between the UE and a network entity, wherein the DCI message is received in a DCI format including a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; as well as An uplink message associated with the timing advance command indicated in the DCI message is sent to the network entity.

26. The method of claim 25, wherein receiving the DCI message comprises: An uplink DCI message is received, wherein the uplink DCI message indicates the timing advance command instead of a scheduling uplink shared channel message or a grant (CG) configuration that activates or releases a configuration.

27. The method of claim 25, wherein receiving the DCI message comprises: A downlink DCI message is received, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing a semi-persistent scheduling (SPS) configuration.

28. A method for wireless communication at a network entity, the method comprising: sending a downlink control information (DCI) message to a user equipment (UE), the downlink control information (DCI) message comprising one or more fields associated with scheduling information for communication between the network entity and the UE, wherein the DCI message is sent in a DCI format, the DCI format comprising a cyclic redundancy check (CRC) scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), the one or more fields being populated with a value indicating that the DCI message includes a timing advance command; as well as An uplink message associated with the timing advance command indicated in the DCI message is received from the UE.

29. The method of claim 28, wherein sending the DCI message comprises: An uplink DCI message is sent, wherein the uplink DCI message indicates the timing advance command instead of a scheduling uplink shared channel message or a grant (CG) configuration that activates or releases a configuration.

30. The method of claim 28, wherein sending the DCI message comprises: A downlink DCI message is sent, wherein the downlink DCI message indicates the timing advance command instead of scheduling a downlink shared channel message or activating or releasing a semi-persistent scheduling (SPS) configuration.

Images