Unified TCI state association for multi-transmit-receive point based communications

Abstract

Systems, methods, processors, and apparatuses are provided for determining a unified TCI state in multi-transmit-receive communications. In one example, a method for a UE includes receiving a plurality of transmit configuration indicator (TCI) states and a unified TCI state to activate / deactivate configurations of Medium Access Control (MAC) Control Elements (CEs) to associate TCI code points in a Downlink Control Information (DCI) format to the TCI states, each TCI code point indicating one or more TCI states; receiving first single transmit receive point downlink control information (sDCI) including one of the plurality of TCI code points; receiving a second sDCI transmitted by scheduling a physical uplink shared channel (PUSCH), wherein the second sDCI indicates one or more of the TCI states associated with the TCI code point of the first sDCI; and in response, transmitting the PUSCH on the basis of the second sDCI.

Description

[0001] Citation of Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 408,894, filed on September 22, 2022, the contents of which are hereby incorporated by reference in their entirety. Background Art

[0003] Multiple transmit receive point (TRP) communication involves a user equipment (UE) exchanging signals with more than one TRP. Multiple TRPs can be integrated into the same base station or different base stations. The UE can communicate with different TRPs using different beams. Data sent and received between the UE and multiple TRPs can be jointly processed to improve reliability, coverage, and capacity performance through flexible deployment scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Some examples of circuits, devices and / or methods will be described below by way of example only.In this context, reference will be made to the accompanying drawings.

[0005] Figure 1 The diagram illustrates a UE communicating with multiple TRPs using multiple beams.

[0006] Figure 2 Illustrated is an exemplary message sequence for multi-TRP communication configuration and data transmission / reception using a unified transmit configuration indicator (TCI) state in accordance with the various aspects described.

[0007] Figure 3 An example of multi-TRP communication using a unified TCI state according to the various aspects described is illustrated.

[0008] Figure 4 Illustrated are exemplary message sequences for multi-TRP communication configuration and data reception during a quasi-co-site (QCL) window in accordance with the various aspects described.

[0009] Figure 5A Two power control (PC) setting lists are illustrated in accordance with various aspects described.

[0010] Figure 5B A list of PC settings according to various aspects described is illustrated.

[0011] Figure 6 Illustrated are exemplary message sequences for multi-TRP communication configuration and data transmission when the PC settings have not been previously configured in accordance with the various aspects described.

[0012] Figure 7An example of multi-TRP communication using a unified TCI state based on fallback downlink control information (DCI) according to the various aspects described is illustrated.

[0013] Figure 8 An exemplary message sequence for multi-TRP or single TRP communication using a unified TCI state based on fallback downlink control information (DCI) according to the various aspects described is illustrated.

[0014] Fig. 9 An example of a multi-TRP configuration using a unified TCI state during a transition from multi-TRP to single-TRP operation in accordance with the various aspects described is illustrated.

[0015] Fig.10 Illustrated are exemplary message sequences for multi-TRP or single TRP communications using a unified TCI state in accordance with the various aspects described.

[0016] Fig.11 An example of multi-TRP uplink configuration and data transmission based on dynamic authorization using a unified TCI state according to the various aspects described is illustrated.

[0017] Fig.12 An exemplary message sequence for multi-TRP uplink configuration and data transmission using a unified TCI state based on dynamic authorization in accordance with the various aspects described is illustrated.

[0018] Fig.13 is a diagram of an example network according to one or more implementations described herein.

[0019] Fig.14 Illustrated is a simplified block diagram of a user equipment wireless communication device in accordance with various aspects described. DETAILED DESCRIPTION

[0020] The present disclosure is described with reference to the accompanying drawings. The accompanying drawings are not drawn to scale, and these drawings are provided only for illustrating the present disclosure. Several aspects of the present disclosure are described below with reference to example applications for illustration. Many specific details, relationships and methods are set forth to provide an understanding of the present disclosure. The present disclosure is not limited by the order of the actions or events illustrated, because some actions can occur in different orders and / or simultaneously with other actions or events. In addition, not all illustrated actions or events are necessary to implement the method according to the selected present disclosure.

[0021] Unified Beam Management Overview

[0022] As the focus of wireless communications moves to higher frequencies, beamforming has become an important aspect of the operation of wireless communication devices. In the downlink, the beam is defined by the transmit configuration indicator (TCI) state. The TCI state includes a source reference signal (e.g., a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB)) and the expected quasi-co-location (QCL) type to be applied. The downlink control information (DCI) that schedules downlink data indicates one or more TCI states for receiving a signal of encoded data. In order to receive a signal based on the indicated TCI state, the UE sets its beamforming coefficients based on the reference signal and QCL type in the TCI state. In the uplink, the beam is indicated by different spatial domain transmit filters. In the DCI that schedules uplink data, the spatial domain transmit filter is identified by a sounding reference signal resource indicator (SRI). In order to send a signal based on the indicated SRI, the UE sets its beamforming coefficients based on the sounding reference signal (SRS) associated with the SRI.

[0023] Early LTE and NR releases support the configuration of separate beams for control channels (e.g., physical uplink control channel (PUCCH) and physical downlink control channel (PDCCH)) and data channels (e.g., physical uplink shared channel (PUSCH) and physical downlink shared channel (PDSCH)). However, due to the signaling overhead required for such granular beam configuration, later releases optimized support for common beam management. In common beam management, certain beams may be configured for more than one channel or signal, including control and data signals in UL, DL, or both UL and DL, as well as CSI-RS and SRS. This reduces signaling overhead because a single TCI state configuration can cover multiple channels and / or reference signals. A beam may be referred to herein as being related to a unified TCI state in both UL and DL. For the purposes of this disclosure, the terms TCI state and unified TCI state may be used interchangeably. The term beam may be used as a shorthand reference to a UE or base station setting that is used to send or receive data based on information associated with a corresponding or associated TCI state.

[0024] Reference now Figure 1 , illustrates a wireless communication network 100 including a UE 101 and three base stations 110, 120, 130. The UE 101 moves through the network 100 along a dashed path in the direction indicated by the arrow. The UE 101 is configured for multi-transmit receive point (TRP) communication, where the UE transmits / receives control and / or user data with respect to more than one TRP. Signals exchanged between the UE and different TRPs may be separated in frequency, time, or space layers. Each base station may include multiple TRPs (e.g., antenna arrays), and different TRPs each provide multiple different TX / RX beams.

[0025] In the illustrated example, TCI state AG has been activated for UE 101. The number of beams that can be activated for the UE is based on the beamforming capability of the UE. Beams A, B, C, F, and G are joint unified TCI states configured for both uplink and downlink. Beam D is a UL unified TCI state, and beam E is a DL unified TCI state. Based on the DCI indicating the TCI state for associated data transmission / reception, UE 101 uses TCI state B to send and receive signals (e.g., PUCCH, PUSCH, PDCCH, PDSCH, CSI-RS, and / or SRS) to a first TRP on base station 110, uses beam E to receive signals (e.g., PDCCH, PDSCH, and / or CSI-RS) from a second TRP on base station 130, and uses beam D to send signals (e.g., PUCCH, PUSCH, and / or SRS) to a second TRP on base station 130. As network or channel conditions change or as the UE moves relative to the base station, different TCI states in the activated TCI state AG may be indicated by subsequent DCI to optimize the quality of the communication link.

[0026] To simplify signaling, the TCI states may be grouped into TCI state pairs, with each TCI state in a pair corresponding to a different TCI state, possibly associated with a different TRP. The network may map a code point to a single TCI state pair (for a single TRP) or two TCI state pairs (for multiple TRPs), with each pair comprising one DL unified TCI state and one UL unified TCI state, or alternatively, a joint unified TCI state. The DCI may then use a single code point to indicate that one or both TCI state pairs should apply. Figure 1 In the DCI, a single code point may indicate that the UE 101 will use TCI state B and TCI state D for the uplink to both TRPs, respectively, and a single code point may indicate that the UE 101 will use TCI state B and TCI state E for the downlink from both TRPs, respectively. Subsequently, when the UE 101 reaches point X on the UE path, the DCI may use different code points to indicate that the UE 101 will use TCI state B and TCI state G for the uplink or downlink or both directions. When the UE is to switch to single-TRP communication, the DCI may communicate using code points indicating a single TCI state (typically applied to both DL and UL) or a single TCI state pair of TCI states AG (one for DL ​​and the other for UL).

[0027] Figure 2is a message flow diagram outlining an example of multi-TRP communication. At 210, a first TRP associated with a base station (e.g., a serving cell) sends radio resource control (RRC) signaling that configures a TCI state pool or list including multiple unified TCI states. The unified TCI states may each be configured for multiple channels and / or signals, such as both data and control channels and reference signals. Some of the indicated unified TCI states may be joint unified TCI states configured for both uplink and downlink channels and / or signals. At 220, the base station sends a medium access control (MAC) control element (CE) that activates up to M combinations (e.g., 8, depending on UE capabilities) of the indicated unified TCI states, each of which includes a single unified TCI state pair (for a single TRP) or multiple unified TCI state pairs (for multiple TRPs). The MAC CE may map different combinations (including a single unified TCI state pair or two unified TCI state pairs) to different TCI code points. The TCI code points in the DCI format are further used to dynamically select a combination from up to "M" activated unified TCI state combinations.

[0028] In multi-TRP communication, there are two types of scheduling schemes: single DCI (sDCI) scheme and multi-DCI (mDCI) scheme. In the sDCI scheme, a single sDCI can schedule PUSCH / PDSCH for two TRPs, while in the mDCI scheme, two DCIs are used, where each corresponding DCI schedules PUSCH / PDSCH for a single corresponding TRP. Therefore, for mDCI, separate DCI signaling is used to configure PUSCH / PDSCH for each TRP, while for sDCI, a single message schedules PUSCH / PDSCH for multiple TRPs. Figure 2 In an example of , sDCI is used. At 225, the base station transmits sDCI indicating (e.g., by code points) a DL unified TCI state pair and a UL unified TCI state pair. The unified TCI state combination indicated by the TCI code points in the sDCI in 225 may include one or more DL unified TCI states, one or more UL unified TCI states, and / or one or more joint (e.g., both UL and DL) TCI states. At 230, the base station transmits sDCI that schedules data reception (e.g., PDSCH) for the UE.

[0029] After the QCL window expires, at 240, the base station transmits the PDSCH, and the UE receives the scheduled PDSCH using the indicated DL unified TCI state pair. The QCL window represents the time it takes for the UE to decode the sDCI and tune its transmitter to the indicated DL unified TCI state. In one example, the UE signals its capabilities to the network in terms of a number of symbols (e.g., 28 symbols or two time slots), and the network assumes the duration of the QCL window based on the UE's signaled capabilities. In one example, the UE uses the information element (IE) timeDurationforQCL to signal its decoding / tuning capabilities to the network.

[0030] At 250, the base station transmits an sDCI scheduling uplink data transmission (e.g., PUSCH) from the UE to the base station. At 260, the UE transmits the PUSCH using the indicated UL unified TCI state pair (e.g., in message 225).

[0031] As the UE moves through coverage areas or network / channel conditions change, different unified TCI states or unified TCI state pairs may be activated per 220. In response to more significant changes in the UE's location or channel / network conditions, different unified TCI state pools may also be indicated by subsequent RRC signaling per 101.

[0032] There are still several open issues regarding common beam management for multi-TRP scenarios, including determining the default TCI state PDSCH during the QCL window, determining the default UE power setting when not configured by an active TCI state, determining the TCI state to assume when PDSCH / PUSCH is scheduled via a fallback DCI without a TCI field, how to support dynamic switching between sTRP and mTRP operation, and determining the TCI state for dynamic grant (DG)-PUSCH for sDCI. This article describes techniques for extending the unified TCI framework to address these and other issues.

[0033] TCI status during the QCL window

[0034] Figure 3 and Figure 4 An exemplary multi-TRP communication configuration and downlink data reception scenario are illustrated. Assume that a TCI state pool or list including multiple unified TCI states has been allocated to UE 101. Figure 3 As shown, a MAC CE 320 is received, which includes a set of activated unified TCI states selected from a TCI state pool, and four TCI state combinations are associated with four code points 000, 001, 010, and 011. Code point 000 corresponds to TCI state 1 (see Figure 31) and configure single TRP communication. Code points 001 and 010 each configure two TCI states for multi-TRP communication with a serving cell and a non-serving cell. Code point 001 configures beam 2 for the serving cell and beam 4 for the non-serving cell, while code point 010 configures beam 3 for the serving cell and beam 6 for the non-serving cell. Code point 011 configures two beams, beam 5 and beam 7, for the non-serving cell. A first sDCI 330 is received, which indicates a unified TCI state 3 and a unified TCI state 6 for downlink data reception (e.g., by using TCI code point 010 in sDCI 330). The TCI state indicated by the most recent sDCI is referred to herein as the currently indicated TCI state.

[0035] The second sDCI 340 is received using a beam associated with TCI state 0, which is assumed to be configured solely for the CORESET. Note that the TCI state of the CORESET may follow one of the active TCI states (i.e., TCI state 3). Ambiguity may arise as to what TCI state the UE should use to receive / buffer PDSCH during the QCL window.

[0036] Figure 4 is an overview Figure 3 Message flow diagram for the scenario. Figure 3 The UE has received multiple TCI code points (e.g., Figure 3 At least two TCI code points among the plurality of TCI code points are each mapped to two different TCI states, and each TCI state is identified by a TCI state identifier (ID). At 430, the UE receives a first sDCI indicating an activated DL TCI state pair using a TCI code point indicating two TCI states among the plurality of TCI code points, the two indicated TCI states including a first TCI state and a second TCI state (e.g., code point 010 indicating TCI state 3 and TCI state 6). At 435, based on a third TCI state (e.g., Figure 4 The UE receives a second sDCI (e.g., Figure 4 sDCI 340). During a predetermined window (e.g., a QCL window) after the time of receiving sDCI 340, the UE adopts one or more TCI states for PDSCH reception based on the configuration of multiple TCI code points of the MAC CE or the third TCI state. At 440, the UE receives the PDSCH via the adopted TCI state.

[0037] When there are two currently indicated DL unified TCI states, the UE may use several methods to adopt the TCI state for PDSCH reception during the QCL window. Figure 3 and Figure 4 The example shown in discloses some exemplary options, where the currently indicated TCI state is TCI state 3 and TCI state 6 configured by the first sDCI 330. In other examples, the currently indicated TCI state may have been indicated in a previously received sDCI or another communication or configuration.

[0038] In the first method, the UE takes Figure 3 and Figure 4 The currently indicated TCI status or beam 3 and beam 6 in the example.

[0039] In the second method, the UE assumes two TCI states indicated by the lowest indicated TCI code point of the multiple TCI code points. In the illustrated example, the UE will assume beam 2 and beam 4 (for code point 001).

[0040] In a third method, the UE assumes a TCI state associated with a CORESET, where the monitored search space has the lowest CORESET ID in the latest timeslot in which one or more CORESETs are monitored by the UE. In the illustrated example, the TCI state is a third TCI state, i.e., TCI state 0 for receiving sDCI 340. In the example of this method, when the physical cell identifiers (PCIs) associated with the two TCI states indicated by the code points included in the first sDCI are associated with a neighboring cell different from the UE's serving cell (e.g., if code point 011 instead of code point 010 has been included in sDCI 330), the UE assumes the third TCI state during the QCL window. In this way, the UE can have a better beam to receive data transmissions than a beam associated with a non-serving cell.

[0041] In the fourth method, the UE adopts one TCI state of the two currently indicated TCI states, or TCI state 3 or TCI state 6 of the illustrated example. In the first example of the method, the TCI state with the smallest TCI ID of the two currently indicated TCI states is adopted (e.g., TCI state 3 in the illustrated example). In the second example of the method, the TCI state with the largest TCI ID of the two currently indicated TCI states is adopted (e.g., TCI state 6 in the illustrated example). In the third example of the method, the UE adopts a TCI state of the two currently indicated TCI states configured with a quasi-co-site (QCL) type A / D source reference signal (RS) on the downlink (DL) bandwidth part (BWP) of the serving cell (e.g., TCI state 3 in the illustrated example). In the fourth example of the method, the UE adopts one TCI state of the two TCI states based on higher layer signaling (e.g., the higher layer signaling configures the first TCI state or the second TCI state of the two currently indicated TCI states (e.g., TCI state 3 (first) or TCI state 6 (second) in the illustrated example)).

[0042] Default power control parameters

[0043] Flexible configuration of power control parameters can support improved multi-TRP communications. For example, as a UE communicating with a first TRP and a second TRP moves toward the first TRP and away from the second TRP, it may be beneficial to reduce the UE's transmit power on the beam associated with the first TRP and increase the transmit power on the beam associated with the second TRP. Power control parameters include 'P0, α of PUSCH, closed loop index I, etc.

[0044] Depending on the configuration, certain power control parameters for uplink transmissions may not be associated with some unified TCI states, resulting in ambiguity about what power control parameter values ​​should be used. To resolve this ambiguity, one or more power control (PC) setting lists may be configured. In one example, the PC setting list may be configured in a bandwidth part (BWP) UL dedicated information element. Each entry in the PC setting list (e.g., addressed by an index value) may be mapped to a unique set of power control parameter values. When one or more of the indicated joint or UL TCI states are not configured with PC parameter settings, the UE may apply a preconfigured or explicitly configured index or entry of the PC setting list as a default PC setting for transmission to the TRP.

[0045] Figure 5A and Figure 5B Two different exemplary methods of PC settings list are shown. Figure 5AIn , a PC setting list is configured for each TRP, and PC setting list 510 is associated with TRP#1, and PC setting list 520 is associated with TRP#2. Figure 5B , the PC setting list 530 includes entries of multiple TRPs in an alternating manner.

[0046] Figure 6 is a message flow diagram outlining an example of a UE applying default PC parameter settings based on a PC setting list. It is assumed that the UE has received a configuration of one or more PC setting lists. Each entry in each of the PC setting lists is associated with one or more TRPs. The UE also receives a configuration of multiple TCI code points, each TCI code point indicating one or more activated UL TCI states. At 630, the UE receives an sDCI scheduled for transmission on a physical uplink shared channel (PUSCH), wherein the sDCI includes a TCI code point indicating two TCI states among the indicated TCI code points. In response to one or both of the two UL TCI states not being associated with a power control setting, at 640, the UE sends a PUSCH based on one or more PC settings mapped to the PC setting list entries selected from the corresponding one or more PC setting lists.

[0047] There are multiple methods for the UE to select a PC setting list entry to determine the PC setting parameter value for the PUSCH. In the first method, the UE applies the PC setting parameter mapped to the PC setting list entry, which has the lowest index value of the corresponding PC setting associated with each of the two TRPs. In the illustrated example, for the beam associated with TRP#1, the UE will select the PC setting value mapped to entry 0 of PC setting list 510, and for the beam associated with TRP#2, the UE will select the PC setting value mapped to entry 0 of PC setting list 520. If PC setting list 530 is used, for the beam associated with TRP#1, the UE will select the PC setting value mapped to entry 0 of PC setting list 530, and for the beam associated with TRP#2, the UE will select the PC setting value mapped to entry 1 of PC setting list 530.

[0048] In the second method, the UE applies PC setting parameters mapped to a PC setting list entry having a preconfigured index value of a corresponding PC setting associated with each of the two TRPs. In the illustrated example, assuming that the preconfigured value of TRP#1 is 1 and the preconfigured index value of TRP#2 is 2, for the beam associated with TRP#1, the UE will select the PC setting value mapped to entry 1 of PC setting list 510, and for the beam associated with TRP#2, the UE will select the PC setting value mapped to entry 2 of PC setting list 520. If PC setting list 530 is used, for the beam associated with TRP#1, the UE will select the PC setting value mapped to entry 2 of PC setting list 530, and for the beam associated with TRP#2, the UE will select the PC setting value mapped to entry 5 of PC setting list 530.

[0049] In a third method, the UE applies the PC settings mapped to the PC settings list entries on the PC settings list associated with a selected one of the different TRPs. Figure 5A PC setting list 510 or 520 of the selected TRP. In one example of the method, the UE applies the PC setting mapped to the PC setting list entry with the lowest identifier on the PC setting list associated with the selected one of the different TRPs. In this example, if TRP #1 is the selected TRP (e.g., TRP #1 is associated with the serving cell), entry 0 of PC setting list 510 will be used.

[0050] TCI status when falling back to DCI scheduling for PUSCH / PDSCH

[0051] Fallback DCI is DCI that includes a reduced number of bits or fields. Fallback DCI that schedules PUSCH or PDSCH may not include TCI state information. This leads to ambiguity about what beam the UE should use to transmit / receive the scheduled data transmission. Figure 7 and Figure 8 An exemplary multi-TRP communication configuration and uplink / downlink data transmission / reception scenario are illustrated. For example, it is assumed that a TCI state pool or list including multiple unified TCI states has been allocated to the UE. It is also assumed that a MAC CE is received, which includes a set of activated unified TCI states selected from the TCI state pool and multiple TCI state combinations each associated with a TCI code point. Figure 7As shown, sDCI 730 was previously received, which indicated UL unified TCI state 3 and UL unified TCI state 7 for uplink data transmission and DL unified TCI state 3 and DL unified TCI state 6 for downlink data reception. At 740, a fallback DCI is received that schedules PUSCH or PDSCH 760. The fallback DCI does not indicate a unified TCI state for PUSCH / PDSCH. Ambiguity may arise as to what TCI state the UE should use to transmit / receive PUSCH / PDSCH 760 scheduled by the fallback DCI.

[0052] Figure 8 is an overview Figure 7 Message flow diagram for the scenario. Figure 7 The UE has received a configuration of multiple TCI code points, each TCI code point indicating one or more activated UL unified TCI states or DL ​​unified TCI states or joint unified TCI states.

[0053] In the uplink scenario, at 830, the UE receives an sDCI indicating two UL unified TCI states (e.g., Figure 7 At 840, the UE receives a subsequent fallback sDCI that configures PUSCH transmission. The fallback sDCI does not indicate a UL unified TCI state for PUSCH (e.g., the sDCI does not include a TCI code point). In response to the fallback sDCI, the UE assumes a default TCI state for PUSCH. In this example, a single TCI state (single TRP) is assumed for sending PUSCH in response to the fallback DCI. This may be desirable when using fallback DCI in situations where beam quality may degrade. At 850, the UE sends PUSCH based on the assumed default UL unified TCI state. In other examples, two default UL unified TCI states are assumed and the UE transmits using two beams.

[0054] In the downlink scenario, at 830, the UE receives an sDCI indicating two DL unified TCI states (e.g., Figure 7At 840, the UE receives a subsequent fallback sDCI that configures the PDSCH transmission. The fallback sDCI does not indicate a DL unified TCI state for the PDSCH (e.g., the sDCI does not include a TCI code point). In response to the fallback sDCI, the UE assumes a default TCI state for the PDSCH. In this example, a single TCI state (single TRP) is assumed for receiving the PDSCH in response to the fallback DCI. This may be desirable when the fallback DCI is used in situations where beam quality may be degraded. At 860, the UE receives the PDSCH based on the assumed default DL unified TCI state. In other examples, two default DL unified TCI states are assumed and the UE receives using two beams.

[0055] There are several methods for determining which unified TCI state the UE takes to send PUSCH or receive PDSCH scheduled by fallback DCI. In the first method, the default UL unified TCI state and / or the default DL unified TCI state are hard-coded in the UE or predefined by the specification and stored in the hardware of one or more processors of the UE.

[0056] In another example, the default unified TCI state is based on two currently indicated uplink TCI states (e.g., Figure 7 3 and TCI state 7 in ) or two currently indicated downlink TCI states (e.g., Figure 7 The first TCI state, the second TCI state, or both TCI states in TCI state 3 and TCI state 6 in the UE are hard-coded in the UE or predefined by the specification and stored in the hardware of one or more processors of the UE. Figure 7 In the UE, if the indication of the "second TCI state" is hard-coded in the UE, the UL unified TCI state 7 will be used to send PUSCH in response to the fallback sDCI, and the DL unified TCI state 6 will be used to receive PDSCH in response to the fallback sDCI.

[0057] In another example, the default unified TCI state is explicitly configured by RRC signaling, MAC CE or DCI. The default TCI state may be indicated by a TCI ID, or as two currently indicated uplink TCI states (e.g., Figure 7 The first TCI state, the second TCI state, or both TCI states in TCI state 3 and TCI state 7 are indicated. Figure 3In the embodiment, if the RRC signaling indicates that the default beam should be "two TCI states", the UL unified TCI state 3 and the UL unified TCI state 7 will be used to send PUSCH in response to the fallback sDCI, and the DL unified TCI state 3 and the DL unified TCI state 6 will be used to receive PDSCH in response to the fallback sDCI.

[0058] PUCCH / PDCCH configuration for dynamic switching between single TRP and multiple TRPs

[0059] As the UE moves through the network or channel or network conditions change, the UE may switch between multi-TRP and single TRP operation. Therefore, a mechanism should be provided for dynamically configuring a unified TCI state for PUCCH and PDCCH as the UE transitions between modes. Fig. 9 and Fig.10 The diagram illustrates a scenario where the UE transitions from multiple TRPs to a single TRP and then back to multiple TRPs.

[0060] exist Fig. 9 In the present invention, there are two currently indicated UL unified TCI states, unified TCI state 3 and unified TCI state 7, which are applied to PUCCH resources configured by RRC signaling; and two currently indicated unified DL TCI states, unified TCI state 3 and unified TCI state 6, which are applied to CORESET resources (e.g., PDCCH) configured by RRC signaling. The currently configured TCI state is indicated by the previously received DCI 970. In one example, when the UE switches from multiple TRPs to a single TRP, RRC signaling 980 indicates which of the two indicated unified TCI states should be used for PUCCH transmission or CORESET resource reception during single TRP operation. The RRC signaling indicates a first TCI state or a second TCI state in the currently indicated TCI state. When the UE switches from a single TRP to multiple TRPs, RRC signaling 990 indicates that both currently indicated unified TCI states for PUCCH and CORESET resource reception should be used for multiple TRP operation. When RRC signaling configures two TCI states (e.g., multi-TRP operation), PUCCH repetition or SFN-based PDCCH or PDCCH repetition may be implicitly enabled. RRC signaling may include two bits that signal a first unified TCI state, a second unified TCI state, or two unified TCI states on a per PUCCH and CORESET resource basis.

[0061] Fig.10 is an overview Fig. 91070 , the UE receives a DCI indicating two unified TCI states for uplink (including PUCCH) and two unified TCI states for downlink (including CORESET resources). At 1080 , the UE receives RRC signaling indicating whether a first unified TCI state, a second unified TCI state, or two currently indicated TCI states should be used for PUCCH transmission and CORESET resource reception. For example, the RRC signaling at 1080 may indicate a first TCI state for PUCCH and two TCI states for CORESET resources. At 1090 , the UE receives a PDCCH via the indicated unified TCI states. In this example, the UE receives PDCCH using beam 3 and beam 6. At 1095, the UE transmits PUCCH via the indicated unified TCI state. In this example, the UE transmits PUCCH using beam 3.

[0062] TCI state mapping for dynamically granted PUSCH

[0063] Dynamically granted PUSCH (as distinct from configured grant-based PUSCH) is scheduled by a specific DCI format. The existing dynamically granted PUSCH scheduling DCI format may be extended or modified to support multi-TRP operation with UL unified TCI state. Fig.11 and Fig.12 An exemplary multi-TRP communication configuration and a dynamic grant PUSCH transmission scenario are illustrated. For example, assume that a TCI state pool including multiple UL unified TCI states has been allocated to UE 101, and a subset of the UL unified TCI states has been activated for the UE. Fig.11 As shown, sDCI 1130 is previously received, which indicates UL unified TCI state 3 and UL unified TCI state 7 for uplink data transmission. At 1150, the UE transmits SRS using UL unified TCI state 6 that has been previously associated with SRI#1. At 1160, a dynamic grant sDCI scheduling PUSCH 1170 is received.

[0064] Fig.12 is an overview Fig.11For example, assume that a TCI state pool or list including multiple unified TCI states has been allocated to the UE. It is also assumed that a MAC CE is received, which includes a set of activated unified TCI states selected from the TCI state pool and multiple TCI state combinations each associated with a TCI code point. At 1230, the UE receives a message indicating two UL unified TCI states (e.g., Figure 7 At 1240, the UE receives a second dynamic grant sDCI that configures PUSCH transmission. The UE determines a UL unified TCI state for transmitting the PUSCH. At 1250, the UE transmits the PUSCH based on the determined UL unified TCI state.

[0065] There are several methods for how a UE determines the UL unified TCI state for a PUSCH based on a dynamic grant. In a first method, the dynamic grant PUSCH scheduling DCI (e.g., sDCI 1160) may be modified or extended to indicate the currently indicated UL unified TCI state (e.g., Fig.11 In one example of the method, the dynamic grant PUSCH scheduling DCI includes a field indicating one of at least three values, wherein the first value corresponds to a first TCI state of two currently indicated uplink TCI states, the second value corresponds to a second TCI state of the two currently indicated uplink TCI states, and the third value corresponds to two TCI states of the two currently indicated uplink TCI states. In one example, the field corresponds to a dedicated bit for dynamic grant (e.g., an existing dynamic grant PUSCH scheduling DCI format is extended to include a new field). In another example, the field is the SRI field of the dynamic grant PUSCH scheduling DCI. Fig.11 In the example of , if sDCI 1160 includes 00 in the TCI field (new field or current SRI field) to indicate that the first UL unified TCI state in the currently indicated UL unified TCI state should be used for PUSCH. In response, the UE sends PUSCH 1170 using beam 3, which is the first UL unified TCI state in the currently indicated UL unified TCI state.

[0066] In the second method, the dynamic grant PUSCH scheduling DCI does not explicitly indicate the UL unified TCI state for PUSCH. In one example of this method, the UE selects the spatial domain transmit filter associated with the most recent SRI to transmit PUSCH. Fig.11In the example of FIG. 11 , in this case (not shown), the UE will use beam 6 for transmitting SRS 1150. After transmitting PUSCH 1170, the UE may transmit subsequent SRS 1180 using SRI#2 associated with unified UL TCI state 3.

[0067] Fig.13 1 is an exemplary network 1300 according to one or more implementations described herein. The exemplary network 1300 may include UE 101-1, UE 101-2, etc. (collectively referred to as "UE 101", and individually referred to as "UE 101"), a radio access network (RAN) 1320, a core network (CN) 1330, an application server 1340, an external network 1350, satellites 1360-1, 1360-2, etc. (collectively referred to as "satellite 1360", and individually referred to as "satellite 1360"). As shown, the network 1300 may include a non-terrestrial network (NTN) including one or more satellites (e.g., of a global navigation satellite system (GNSS)) 1360 in communication with the UE 101 and the RAN 1320.

[0068] The systems and devices of the exemplary network 1300 may operate in accordance with one or more communication standards, such as the 2nd generation (2G) communication standards of the 3rd Generation Partnership Project (3GPP), the 3rd generation (3G) communication standards, the 4th generation (4G) (e.g., Long Term Evolution (LTE)) communication standards, and / or the 5th generation (5G) (e.g., New Radio (NR)) communication standards. Additionally or alternatively, one or more of the systems and devices of the exemplary network 1300 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., the 6th generation (6G) standards, the 7th generation (7G) standards, etc.), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., Wireless Metropolitan Area Networks (WMAN), Worldwide Interoperability for Microwave Access (WiMAX), etc.), and more.

[0069] As shown, UE 101 may include a smart phone (e.g., a handheld touch screen mobile computing device capable of connecting to one or more wireless communication networks). Additionally or alternatively, UE 101 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld terminal, etc. In some specific implementations, UE 101 may include an Internet of Things (IoT) device (or IoT UE), which may include a network access layer designed for low-power IoT applications that utilize transient UE connections. Additionally or alternatively, IoT UEs may utilize one or more types of technologies such as machine-to-machine (M2M) communication or machine-type communication (MTC) (e.g., to exchange data with an MTC server or other device via a public land mobile network (PLMN)), proximity services (ProSe) or device-to-device (D2D) communication, sensor networks, IoT networks, and more. Depending on the scenario, the M2M or MTC exchange of data may be a machine-initiated exchange, and the IoT network may include IoT UEs interconnected with transient connections (which may include uniquely identifiable embedded computing devices within the Internet infrastructure). In some scenarios, the IoT UE may execute background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0070] UE 101 may communicate and establish connections with one or more other UEs 101 via one or more radio channels 1312, each of which may include a physical communication interface / layer. The connection may include an M2M connection, an MTC connection, a D2D connection, etc. In some implementations, UE 101 may be configured to discover each other, negotiate radio resources between each other, and establish connections between each other without intervention or communication involving a RAN node 1322 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc. may involve communication with a RAN node 1322 or another type of network node.

[0071] UE 101 may communicate with RAN 1320 and establish a connection therewith (e.g., communicatively coupled), which may involve one or more radio channels 1314-1 and 1314-2, each of which may include a physical communication interface / layer. In some implementations, the UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a UE capable of multiple receptions and transmissions (Rx / Tx) may use resources provided by different network nodes (e.g., 1322-1 and 1322-2), which may be connected via a non-ideal backhaul (e.g., where one of the network nodes provides NR access and the other network node provides E-UTRA for LTE or NR access for 5G). In such a scenario, one network node may act as a master node (MN) and the other node may act as a secondary node (SN). The MN and the SN may be connected via a network interface, and at least the MN may be connected to CN 1330. Additionally, at least one of the MN or the SN may operate with shared spectrum channel access, and the functionality specified for the UE 1310 may be used for an integrated access and backhaul mobile terminal (IAB-MT). Similar to the UE 1310, the IAB-MT may access the network using one network node or using two different nodes with an enhanced dual connectivity (EN-DC) architecture, a new radio dual connectivity (NR-DC) architecture, etc. In some implementations, a base station (as described herein) may be an example of a network node 1322.

[0072] As described herein, UE 101-2 may operate in a multi-TRP mode, wherein the UE communicates with multiple transmit receive points (TRPs) (e.g., a TRP associated with network node 1322-1 and a TRP associated with network node 1322-2) simultaneously in channel 1314-2 using multiple unified TCI states. UE 101-2 is configured to receive, store, and process multi-TRP unified TCI state information, which enables UE 101-2 to perform the functions described above with respect to common beam management for multi-TRP operation. Multi-TRP unified TCI state information may include instructions or algorithms used by the UE for determining a default TCI state PDSCH during a QCL window, determining a default UE power setting when not configured by an active TCI state, determining a TCI state to be taken when scheduling PDSCH / PUSCH via a fallback DCI without a TCI field, how to support dynamic switching between sTRP and mTRP operations, and determining a TCI state for a dynamic grant (DG)-PUSCH of sDCI. The multi-TRP unified TCI state information may also include pre-configured or pre-coded values ​​of the default unified TCI state according to the specification.

[0073] As shown, UE 101 may also or alternatively be connected to access point (AP) 1316 via connection interface 1318, which may include an air interface that enables UE 101 to communicatively couple with AP 1316. AP 1316 may include a wireless local area network (WLAN), a WLAN node, a WLAN termination point, etc. The connection to AP 1316 may include a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 1316 may include a wireless fidelity router or other AP. Fig.13 1316. Although not explicitly depicted in the drawings, AP 1316 may be connected to another network (e.g., the Internet) without being connected to RAN 1320 or CN 1330. In some scenarios, UE 101, RAN 1320, and AP 1316 may be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE WLAN radio level integration with IPsec tunneling (LWIP) technology. LWA may involve UE 101 in RRC_CONNECTED state being configured by RAN 1320 to utilize radio resources of LTE and WLAN. LWIP may involve UE 101 using WLAN radio resources (e.g., connection interface 1318) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 1318. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0074] The RAN 1320 may include one or more RAN nodes 1322-1 and 1322-2 (collectively, RAN nodes 1322, and individually, RAN nodes 1322), which enable channels 1314-1 and 1314-2 to be established between the UE 101 and the RAN 1320. The RAN node 1322 may include a network access point configured to provide a radio baseband function for data and / or voice connections between a user and a network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, as an example, the RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, an NR base station, a next generation eNB (gNB), etc.). The RAN node 1322 may include a roadside unit (RSU), a transmit receive point (TRxP or TRP), and one or more other types of ground stations (e.g., ground access points). In some scenarios, the RAN node 1322 may be a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell, etc. having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell. As described below, in some implementations, the satellite 1360 may operate as a base station (e.g., a RAN node 1322) relative to the UE 101. Therefore, references herein to a base station, a RAN node 1322, etc. may relate to implementations in which the base station, the RAN node 1322, etc. are terrestrial network nodes, as well as implementations in which the base station, the RAN node 1322, etc. are non-terrestrial network nodes (e.g., a satellite 1360).

[0075] Some or all or portions of the RAN nodes 1322 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers may be operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities may be operated by individual RAN nodes 1322; a medium access control (MAC) / physical (PHY) layer split, where the RRC, PDCP, radio link control (RLC), and MAC layers may be operated by the CRAN / vBBUP, and the PHY layer may be operated by individual RAN nodes 1322; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer may be operated by the CRAN / vBBUP, and the lower portions of the PHY layer may be operated by individual RAN nodes 1322. The virtualization framework may allow idle processor cores of the RAN node 1322 to perform or execute other virtualized applications.

[0076] In some implementations, the separate RAN nodes 1322 may represent separate gNB distributed units (DUs) connected to a gNB control unit (CU) via separate F1 or other interfaces. In such implementations, the gNB-DU may include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU may be operated by a server (not shown) located in the RAN 1320 or by a server pool (e.g., a group of servers configured to share resources) in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 1322 may be next generation eNBs (i.e., gNBs) that may provide Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 101 and may be connected to the 5G core network (5GC) 1330 via an NG interface.

[0077] Any of the RAN nodes 1322 may serve as an endpoint for an air interface protocol and may be the first point of contact for the UE 101. In some implementations, any of the RAN nodes 1322 may perform various logical functions of the RAN 1320, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling and mobility management. The UE 101 may be configured to communicate with each other or with any of the RAN nodes 1322 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink (SL) communications), but the scope of such implementations may not be limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0078] In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 1322 to the UE 101, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid (e.g., a resource grid or a time-frequency resource grid) that represents the physical resources for the downlink in each time slot. Such a time-frequency plane representation is common for OFDM systems, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block may include a set of resource elements (REs); in the frequency domain, this may represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transport several different physical downlink channels.

[0079] In addition, the RAN node 1322 may be configured to wirelessly communicate with the UE 101 and / or with each other via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band"), an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"), or a combination thereof. For example, the licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz band. The licensed spectrum may correspond to a channel or frequency band that is selected, reserved, regulated, etc. for certain types of wireless activities (e.g., wireless telecommunications network activities), and the unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activities. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public sector organization (e.g., a government agency, a regulatory agency, etc.) or frequency allocations determined by a private sector organization involved in developing wireless communication standards and protocols, etc.

[0080] To operate in an unlicensed spectrum, the UE 101 and the RAN node 1322 may perform one or more known medium sensing operations or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0081] UE 101 may implement various technologies for communicating via licensed and unlicensed spectrum. Examples of such technologies may include licensed assisted access (LAA) and NR unlicensed (NR-U), which may include anchored NR-U and independent NR-U. The LAA mechanism may be built based on the carrier aggregation (CA) technology of the advanced LTE system. In CA, each aggregated carrier is referred to as a component carrier (CC). In some cases, each CC may have a different bandwidth from other CCs. In a time division duplex (TDD) system, the number of CCs and the bandwidth of each CC may be the same for DL ​​and UL. CA also includes individual service cells to provide individual CCs. The coverage of the service cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary service cell or PCell may provide a primary component carrier (PCC) for both UL and DL, and may handle RRC and non-access stratum (NAS) related activities. Other service cells are referred to as SCells, and each SCell may provide a single secondary component carrier (SCC) for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 101 to undergo switching.

[0082] In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by a PCell operating in a licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive an UL grant on the configured LAA SCell, indicating different PUSCH start positions within the same subframe. In order to operate in an unlicensed spectrum, the UE 101 and the RAN node 1322 may also operate using unlicensed spectrum via anchored NR-U and independent NR-U operations, where the UE may be configured with a PCell in the unlicensed spectrum in addition to any SCell. In anchored NR-U, the UE 101 may use dual connectivity by communicating with an LTE anchor base station using licensed spectrum and communicating with an NR-U node using unlicensed spectrum. Alternatively, the UE 101 may use CA by communicating with an NR anchor base station using licensed spectrum and communicating with an NR-U node using unlicensed spectrum. Standalone NR-U may involve a scenario where UE 101 communicates with the network only via an NR-U node.

[0083] The PDSCH may carry user data and higher layer signaling to the UE 101. The physical downlink control channel (PDCCH) may carry information about, among other things, transport formats and resource allocations associated with the PDSCH channel. The PDCCH may also inform the UE 101 about transport formats, resource allocations, and hybrid automatic repeat request (HARQ) information associated with uplink shared channels. Typically, downlink scheduling (e.g., allocating control and shared channel resource blocks to UE 101-2 within a cell) may be performed on any of the RAN nodes 1322 based on channel quality information fed back from any of the UEs 101. Downlink resource assignment information may be sent on the PDCCH for (e.g., assigned to) each of the UEs 101.

[0084] PDCCH uses control channel elements (CCE) to convey control information, where several CCEs (e.g., 6, etc.) may be composed of resource element groups (REGs), where REGs are defined as physical resource blocks (PRBs) in OFDM symbols. Before being mapped to resource elements, PDCCH complex-valued symbols may first be organized into quaternions, which may then be arranged, for example, using a sub-block interleaver for rate matching. One or more of these CCEs may be used to send each PDCCH, where each CCE may correspond to nine sets of four physical resource elements, referred to as REGs. Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs may be used to send the PDCCH. Four or more different PDCCH formats may be defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16).

[0085] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to send EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREGs. In some cases, an ECCE may have other numbers of EREGs.

[0086] The RAN nodes 1322 may be configured to communicate with each other via an interface 1323. In an implementation where the system is an LTE system, the interface 1323 may be an X2 interface. In an NR system, the interface 1323 may be an Xn interface. The X2 interface may be defined between two or more RAN nodes 1322 (e.g., two or more eNBs / gNBs or a combination thereof) connected to an evolved packet core (EPC) or CN 1330, or between two eNBs connected to the EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface, and may be used to convey information about the delivery of user data between eNBs or gNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the master eNB (MeNB) to the secondary eNB (SeNB); information about successful in-sequence delivery of PDCP packet data units (PDUs) from the SeNB to the UE 101 for user data; information about PDCP PDUs that are not delivered to the UE 101; information about the current minimum expected buffer size at the SeNB for sending user data to the UE; etc. X2-C may provide intra-LTE access mobility functions (e.g., including context transfer from the source eNB to the target eNB, user plane transmission control, etc.), load management functions, and inter-cell interference coordination functions.

[0087] As shown, RAN 1320 may be connected (e.g., communicatively coupled) to CN 1330. CN 1330 may include a plurality of network elements 1332 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 1330 via RAN 1320. In some implementations, CN 1330 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. The components of CN 1330 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) may be used to virtualize any or all of the above network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1330 may be referred to as a network slice, and a logical instance of a portion of CN 1330 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architecture and infrastructure can be used to virtualize one or more network functions onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0088] As shown, CN 1330, application server 1340 and external network 1350 may be connected to each other via interfaces 1334, 1336 and 1338, which may include IP network interfaces. Application server 1340 may include one or more server devices or network elements (e.g., virtual network functions (VNFs)) that provide applications (e.g., universal mobile telecommunications system packet service (UMTS PS) domain, LTE-PS data services, etc.) that use IP bearer resources with CN1330. Application server 1340 may also or alternatively be configured to support one or more communication services (e.g., IP voice (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UE 101 via CN 1330. Similarly, external network 1350 may include one or more networks of various networks, including the Internet, thereby providing network access to various additional services, information, interconnectivity and other network features to mobile communication networks and UE 101.

[0089] As shown, exemplary network 1300 may include an NTN that may include one or more satellites 1360-1 and 1360-2 (collectively, "satellites 1360"). Satellites 1360 may communicate with UE 101 via a serving link or wireless interface 1362 and / or communicate with RAN 1320 via a feeder link or wireless interface 1364 (depicted as 1364-1 and 1364-2, respectively). In some implementations, satellite 1360 may operate as a passive or transparent network relay node with respect to communications between UE 101 and a terrestrial network (e.g., RAN 1320). In some implementations, satellite 1360 may operate as an active or regenerative network node, such that satellite 1360 may operate as a base station for UE 101 (e.g., as a gNB of RAN 1320) with respect to communications between UE 101 and RAN 1320. In some implementations, the satellites 1360 can communicate with each other via a direct wireless interface (e.g., 1366) or an indirect wireless interface (e.g., via the RAN 1320 using interfaces 1364-1 and 1364-2).

[0090] Additionally or alternatively, satellite 1360 may include a GEO satellite, a LEO satellite, or another type of satellite. Satellite 1360 may also or alternatively relate to one or more satellite systems or architectures, such as a global navigation satellite system (GNSS), a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), etc. In some specific implementations, satellite 1360 may operate as a base station (e.g., RAN node 1322) relative to UE 101. Therefore, references to base stations, RAN nodes 1322, etc. herein may relate to specific implementations in which base stations, RAN nodes 1322, etc. are ground network nodes, as well as specific implementations in which base stations, RAN nodes 1322, etc. are non-ground network nodes (e.g., satellite 1360). As described herein, UE 101 and base stations, RAN nodes 1322, etc. may communicate with each other via interface 1314 to implement enhanced power saving techniques.

[0091] Fig.141400 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 1400 may include at least an application circuit 1402, a baseband circuit 1404, an RF circuit 1406, a front end module (FEM) circuit 1408, one or more antennas 1410, and a power management circuit (PMC) 1412 coupled together as shown. The components of the illustrated device 1400 may be included in a UE or a RAN node. In some implementations, the device 1400 may include fewer elements (e.g., the RAN node may not utilize the application circuit 1402, but instead include a processor / controller to process IP data received from the CN or the Evolved Packet Core (EPC)). In some implementations, the device 1400 may include additional elements, such as a memory / storage device, a display, a camera, a sensor (including one or more temperature sensors, such as a single temperature sensor, multiple temperature sensors located at different locations in the device 1400, etc.) or an input / output (I / O) interface. In other implementations, the components described below may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a Cloud-RAN (C-RAN) implementation).

[0092] The application circuit 1402 may include one or more application processors. For example, the application circuit 1402 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 1400. In some specific implementations, the processor of the application circuit 1402 may process IP data packets received from the EPC.

[0093] The baseband circuit 1404 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 1404 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 1406 and generate baseband signals for the transmit signal path of the RF circuit 1406. The baseband circuit 1404 may interact with the application circuit 1402 to generate and process baseband signals and control the operation of the RF circuit 1406. For example, in some specific implementations, the baseband circuit 1404 may include a 3G baseband processor 1404A, a 4G baseband processor 1404B, a 5G baseband processor 1404C, or other baseband processors 1404D for other existing generations, generations under development, or generations to be developed in the future (e.g., 5G, 6G, etc.). The baseband circuit 1404 (e.g., one or more baseband processors 1404A-D) may handle various radio control functions that may communicate with one or more radio networks via the RF circuit 1406. In other implementations, some or all of the functionality of baseband processors 1404A-D may be included in a module stored in memory 1404G and executed via central processing unit (CPU) 1404E.

[0094] The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, the modulation / demodulation circuitry of the baseband circuitry 1404 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some implementations, the encoding / decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and in other aspects may include other suitable functions.

[0095] In some specific implementations, the memory 1404G may store and process multi-TRP unified TCI state information, which enables the device 1400 to perform the functions described above regarding common beam management of multi-TRP operation. The multi-TRP unified TCI state information may include instructions that, when executed by the BB processor 1404C or the CPU 1404E, enable the device to perform methods for: determining the default TCI state PDSCH during the QCL window, determining the default UE power setting when not configured by the active TCI state, determining the TCI state to be taken when scheduling PDSCH / PUSCH via a fallback DCI without a TCI field, how to support dynamic switching between sTRP and mTRP operations, and determining the TCI state for the dynamic grant (DG)-PUSCH of sDCI. The multi-TRP unified TCI state information may also include pre-configured or precoded values ​​for the default unified TCI state according to the specification.

[0096] In some implementations, the baseband circuit 1404 may include one or more audio digital signal processors (DSPs) 1404F. The audio DSP 1404F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other implementations. In some implementations, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some implementations, some or all of the constituent components of the baseband circuit 1404 and the application circuit 1402 may be implemented together, for example, on a system on a chip (SOC).

[0097] In some implementations, the baseband circuitry 1404 may provide communications compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 1404 may support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Implementations in which the baseband circuitry 1404 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0098] RF circuit 1406 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various specific implementations, RF circuit 1406 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1406 may include a receive signal path, which may include circuits that down-convert RF signals received from FEM circuit 1408 and provide baseband signals to baseband circuit 1404. RF circuit 1406 may also include a transmit signal path, which may include circuits that up-convert baseband signals provided by baseband circuit 1404 and provide RF output signals to FEM circuit 1408 for transmission.

[0099] In some implementations, the receive signal path of the RF circuit 1406 may include a mixer circuit 1406A, an amplifier circuit 1406B, and a filter circuit 1406C. In some implementations, the transmit signal path of the RF circuit 1406 may include a filter circuit 1406C and the mixer circuit 1406A. The RF circuit 1406 may also include a synthesizer circuit 1406D for synthesizing frequencies used by the mixer circuit 1406A of the receive signal path and the transmit signal path. In some implementations, the mixer circuit 1406A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1408 based on the synthesized frequency provided by the synthesizer circuit 1406D. The amplifier circuit 1406B may be configured to amplify the down-converted signal, and the filter circuit 1406C may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1404 for further processing. In some implementations, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some implementations, the mixer circuit 1406A of the receive signal path may include a passive mixer, but the scope of the implementation is not limited in this respect.

[0100] In some implementations, the mixer circuit 1406A of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 1406D to generate an RF output signal for the FEM circuit 1408. The baseband signal can be provided by the baseband circuit 1404 and can be filtered by the filter circuit 1406C.

[0101] In some implementations, the mixer circuit 1406A of the receive signal path and the mixer circuit 1406A of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some implementations, the mixer circuit 1406A of the receive signal path and the mixer circuit 1406A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some implementations, the mixer circuit 1406A of the receive signal path and the mixer circuit 1406A of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some implementations, the mixer circuit 1406A of the receive signal path and the mixer circuit 1406A of the transmit signal path may be configured for superheterodyne operation.

[0102] In some implementations, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the implementation is not limited in this respect. In some alternative implementations, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative implementations, RF circuit 1406 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1404 may include a digital baseband interface to communicate with RF circuit 1406.

[0103] In some dual-mode implementations, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the implementations is not limited in this respect.

[0104] In some implementations, synthesizer circuit 1406D can be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the implementation is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1406D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0105] The synthesizer circuit 1406D can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1406A of the RF circuit 1406. In some implementations, the synthesizer circuit 1406D can be a fractional-N / N+1 synthesizer.

[0106] In some implementations, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 1404 or the application circuit 1402 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1402.

[0107] The synthesizer circuit 1406D of the RF circuit 1406 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some implementations, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry output) to provide a fractional division ratio. In some example implementations, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these implementations, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0108] In some implementations, the synthesizer circuit 1406D can be configured to generate a carrier frequency as an output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some implementations, the output frequency can be an LO frequency (fLO). In some implementations, the RF circuit 1406 can include an IQ / polarity converter.

[0109] The FEM circuitry 1408 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1410, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1406 for further processing. The FEM circuitry 1408 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 1406 for transmission via one or more of the one or more antennas 1410. In various implementations, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 1406, only in the FEM circuitry 1408, or in both the RF circuitry 1406 and the FEM circuitry 1408.

[0110] In some implementations, the FEM circuit 1408 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuit 1406). The transmit signal path of the FEM circuit 1408 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 1406); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 1410). The transmit and receive signal paths may include parallel components with beamforming capabilities to enable multi-TRP operation, in which communication is performed simultaneously via multiple beams.

[0111] In some implementations, the PMC 1412 can manage the power provided to the baseband circuit 1404. Specifically, the PMC 1412 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 1400 is capable of being powered by a battery, for example, when the device is included in a UE, the PMC 1412 can generally be included. The PMC 1412 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0112] Although Fig.14 The PMC 1412 is shown coupled only to the baseband circuit 1404. However, in other implementations, the PMC 1412 may additionally or alternatively be coupled to other components (such as, but not limited to, the application circuit 1402, the RF circuit 1406, or the FEM circuit 1408) and perform similar power management operations.

[0113] In some implementations, the PMC 1412 can control or otherwise be part of various power saving mechanisms of the device 1400. For example, if the device 1400 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 1400 can be powered off for short time intervals, thereby saving power.

[0114] If there is no data traffic activity for an extended period of time, the device 1400 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1400 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 1400 may not receive data in this state; in order to receive data, the device may transition back to the RRC_Connected state.

[0115] An additional power saving mode can prevent a device from using the network for a period longer than the paging interval (which can range from a few seconds to several hours). During this period, the device cannot connect to the network and can be completely powered down. Any data transmitted during this period will be significantly delayed, assuming that the delay is acceptable.

[0116] The processor of the application circuit 1402 and the processor of the baseband circuit 1404 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1404 can be used alone or in combination to perform the functions of layer 3, layer 2, or layer 1, and the processor of the baseband circuit 1404 can utilize data received from these layers (e.g., packet data) and further perform the functions of layer 4 (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layer). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0117] Above are several flow charts outlining example methods and exchanges of messages. In this specification and the appended claims, the use of the term "determine" in reference to some entities (e.g., parameters, variables, etc.) when describing method steps or functions is interpreted broadly. For example, "determine" is interpreted to cover communications such as receiving and parsing an encoded entity or value of an entity. "Determine" should be interpreted to cover accessing and reading a memory (e.g., a lookup table, a register, a device memory, a remote memory, etc.) storing an entity or a value for an entity. "Determine" should be interpreted to cover calculating or deriving an entity or a value of an entity based on other quantities or entities. "Determine" should be interpreted to cover any way of inferring or identifying an entity or a value of an entity.

[0118] As used herein, the term identify, when used with reference to an entity or a value of an entity, is to be broadly interpreted to encompass any manner of determining an entity or a value of an entity. For example, the term identify is to be interpreted to encompass communications such as receiving and parsing an encoded entity or a value of an entity. The term identify should be interpreted to encompass accessing and reading a memory storing an entity or a value for an entity (e.g., a device queue, a lookup table, a register, a device memory, a remote memory, etc.).

[0119] As used herein, the term "encoding" when used with reference to some entity or value of an entity is to be broadly interpreted to encompass any manner or technique for generating a data sequence or signal that communicates the entity to another component.

[0120] As used herein, the term "select" when used with reference to an entity or value of an entity is to be interpreted broadly to encompass any manner of determining an entity or value of an entity from a plurality or a series of possible choices. For example, the term "select" is to be interpreted as encompassing accessing and reading a memory (e.g., a lookup table, register, device memory, remote memory, etc.) storing an entity or value for an entity and returning an entity or entity value from those stored. The term "select" is to be interpreted as applying one or more constraints or rules to a set of input parameters to determine an appropriate entity or entity value. The term "select" is to be interpreted broadly to encompass any manner of selecting an entity based on one or more parameters or conditions.

[0121] As used herein, the term "derive" is to be interpreted broadly when used with reference to an entity or a value of an entity. "Derivation" should be interpreted to encompass accessing and reading a memory (e.g., a lookup table, a register, a device memory, a remote memory, etc.) that stores some initial or base values, and performing processing and / or logical / mathematical operations on one or more values ​​to generate a derived entity or a value for an entity. "Derivation" should be interpreted to encompass calculating or measuring an entity or a value of an entity based on other quantities or entities. "Derivation" should be interpreted to encompass any way of inferring or identifying an entity or a value of an entity.

[0122] As used herein, the term "indication," when used with reference to an entity (e.g., a parameter or setting) or the value of an entity, is to be broadly interpreted to encompass any manner of conveying an entity or the value of an entity, either explicitly or implicitly. For example, bits within a sent message may be used to explicitly encode the value of an indication, or may encode an index or other indicator that is mapped to the value of an indication by a previous configuration. The absence of a field in a message may implicitly indicate the value of an entity based on a previous configuration.

[0123] Examples herein may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium comprising executable instructions that, when executed by a machine or circuit (e.g., a processor with memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described specific implementations and examples.

[0124] Embodiment 1 is a device for user equipment (UE), the device comprising one or more processors, the one or more processors being configured to enable the UE to: receive multiple transmission configuration indicator (TCI) states and a unified TCI state activation / deactivation configuration of a medium access control (MAC) control element (CE) to associate multiple TCI code points in a downlink control information (DCI) format to the TCI states, wherein at least two of the multiple TCI code points are each mapped to two different TCI states; receive first single downlink control information (sDCI), wherein the first sDCI includes one of the multiple TCI code points; receive a second sDCI scheduling PDSCH reception at a reception time; and during a predetermined window after the reception time, determine one or more TCI states to be adopted for the PDSCH reception based on at least one TCI code point among the multiple TCI code points or the TCI state used to receive the second sDCI.

[0125] Embodiment 2 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the first sDCI includes a TCI code point among the multiple TCI code points indicating two TCI states including a first TCI state and a second TCI state, and further, wherein the one or more processors are configured to assume the two TCI states indicated by the TCI code points included in the first sDCI during the predetermined window after the reception time of the second sDCI.

[0126] Embodiment 3 includes the subject matter of embodiment 1, including or omitting optional elements, wherein during the predetermined window after the reception time of the second sDCI, the one or more processors are configured to assume two TCI states indicated by the lowest TCI code point among the multiple TCI code points indicating two TCI states.

[0127] Embodiment 4 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the one or more processors are configured to assume the TCI state for receiving the second sDCI during the predetermined window.

[0128] Embodiment 5 includes the subject matter of embodiment 4, including or omitting optional elements, wherein the TCI state used to receive the second sDCI corresponds to a monitored search space having the lowest CORESET in the latest time slot of a control resource set (CORESET) monitored by the UE.

[0129] Embodiment 6 includes the subject matter of embodiment 4, including or omitting optional elements, wherein the one or more processors are configured to adopt the TCI state for receiving the second sDCI during the predetermined window when the physical cell identifier (PCI) associated with the two TCI states indicated by the TCI code point included in the sDCI is associated with a neighboring cell that is different from a serving cell of the UE.

[0130] Embodiment 7 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the first sDCI includes a TCI code point among the multiple TCI code points indicating two TCI states including a first TCI state and a second TCI state, and further, wherein during the predetermined window, the one or more processors are configured to assume one of the two TCI states indicated by the code point included in the first sDCI.

[0131] Embodiment 8 includes the subject matter of Embodiment 7, including or omitting optional elements, wherein during the predetermined window, the one or more processors are configured to assume the TCI state having the smallest TCI ID of the two TCI states.

[0132] Embodiment 9 includes the subject matter of embodiment 7, including or omitting optional elements, wherein during the predetermined window, the one or more processors are configured to assume the TCI state having the largest TCI ID of the two TCI states.

[0133] Embodiment 10 includes the subject matter of embodiment 7, including or omitting optional elements, wherein during the predetermined window, the one or more processors are configured to assume one of the two TCI states in which a quasi-co-site (QCL) type A / D source reference signal (RS) is configured on a downlink (DL) bandwidth part (BWP) of the serving cell.

[0134] Embodiment 11 includes the subject matter of embodiment 7, including or omitting optional elements, wherein during the predetermined window, the one or more processors are configured to assume one of the two TCI states based on higher layer signaling.

[0135] Embodiment 12 is a device of a user equipment (UE), the device comprising: a memory and one or more processors, the one or more processors being configured to execute instructions stored in the memory so that the UE: receives a configuration of one or more power control (PC) setting lists, wherein each entry in each of the PC setting lists is associated with one or more transmit receive points (TRPs); receives a configuration of multiple transmit configuration indicator (TCI) code points, each TCI code point indicating one or more activated uplink (UL) TCI states; receives single downlink control information (sDCI), wherein the sDCI includes a TCI code point indicating two UL TCI states among the multiple TCI code points, each of the two UL TCI states being associated with one of two different transmit receive points (TRPs); and in response to one or both of the two UL TCI states being not associated with a power control setting, sends a PUSCH transmission based on one or more PC settings selected from the corresponding one or more PC setting lists.

[0136] Embodiment 13 includes the subject matter of Embodiment 12, including or omitting optional elements, wherein each of the one or more PC setting lists is associated with a different TRP of the two different TRPs.

[0137] Embodiment 14 includes the subject matter of embodiment 12, including or omitting the optional element, wherein every other entry on the single PC settings list is associated with a different TRP of the two different TRPs.

[0138] Embodiment 15 comprises the subject matter of embodiment 12, including or omitting optional elements, wherein the one or more processors are configured to send the PUSCH based on the corresponding PC settings mapped to a PC settings list entry, the PC settings list entry having a lowest index value of the corresponding PC settings list associated with each of the two different TRPs.

[0139] Embodiment 16 comprises the subject matter of embodiment 12, including or omitting optional elements, wherein the one or more processors are configured to send the PUSCH based on the corresponding PC settings mapped to the PC setting list entries identified by the index values ​​of the corresponding PC setting list, wherein the index values ​​are preconfigured by a higher layer for each of the two different TRPs.

[0140] Embodiment 17 comprises the subject matter of embodiment 12, including or omitting optional elements, wherein the one or more processors are configured to send the PUSCH based on the PC settings mapped to the PC setting list entries on the PC setting list associated with the two different TRPs.

[0141] Embodiment 18 comprises the subject matter of embodiment 17, including or omitting optional elements, wherein the one or more processors are configured to send the PUSCH based on two PC settings mapped to PC setting list entries, the PC setting list entries having a lowest identifier and a second lowest identifier on the PC setting list associated with the two different TRPs.

[0142] Embodiment 19 is a device for a user equipment (UE), the device comprising one or more processors, the one or more processors being configured to: receive multiple transmission configuration indicator (TCI) states and a unified TCI state activation / deactivation configuration of a medium access control (MAC) control element (CE) to associate TCI code points in a downlink control information (DCI) format to the TCI states, each TCI code point indicating one or more TCI states; receive a first single downlink control information (sDCI), wherein the first sDCI comprises one TCI code point among the multiple TCI code points; receive a second sDCI scheduling a PUSCH transmission or a PDSCH reception, wherein the subsequent sDCI does not include a TCI code point; and in response to the second sDCI, send the PUSCH transmission or receive the PDSCH reception based on a default uplink TCI state or a default downlink TCI state.

[0143] Embodiment 20 includes the subject matter of embodiment 19, including or omitting optional elements, wherein the default uplink TCI state or the default downlink TCI state is hard-coded or predefined by a specification and stored in hardware of the one or more processors of the UE.

[0144] Embodiment 21 includes the subject matter of embodiment 20, including or omitting optional elements, wherein the first sDCI includes a TCI code point among the multiple TCI code points indicating two uplink TCI states or two downlink TCI states, and further, wherein the default uplink TCI state is predefined in the specification as the first TCI state or the second TCI state among the two uplink TCI states, or the default downlink state is predefined in the specification as the first TCI state or the second TCI state among the two downlink TCI states.

[0145] Embodiment 22 includes the subject matter of embodiment 19, including or omitting optional elements, wherein the first sDCI includes a TCI code point indicating two uplink TCI states or two downlink TCI states among the multiple TCI code points, and further, wherein the default uplink TCI state or the default downlink TCI state is explicitly configured as the first TCI state or the second TCI state among the two uplink TCI states or the two downlink TCI states through radio resource control (RRC) signaling, medium access control (MAC) control element (CE) or DCI.

[0146] Embodiment 23 is an apparatus for a user equipment (UE), the apparatus comprising one or more processors, the one or more processors being configured to: receive a plurality of transmission configuration indicator (TCI) states and a configuration of a unified TCI state activation / deactivation medium access control (MAC) control element (CE) to associate a plurality of TCI code points in a downlink control information (DCI) format to the TCI states, wherein at least two of the plurality of TCI code points are each mapped to two different TCI states; receive a first single downlink control information (sDCI), wherein the first sDCI comprises the plurality of TCI states; The indication in the CI code point includes TCI code points of two TCI states, a first TCI state and a second TCI state; receiving corresponding configurations for physical uplink control channel (PUCCH) resources or control resource set (CORESET) resources via radio resource control (RRC) signaling, and indications of the first TCI state or the second TCI state or both the first TCI state and the second TCI state for the PUCCH resources or the CORESET resources, respectively; and in response, sending PUCCH or receiving PDCCH based on the TCI state indicated by the RRC signaling.

[0147] Embodiment 24 includes the subject matter of embodiment 23, including or omitting optional elements, wherein the RRC configuration includes a field encoding one of at least three values, wherein the first value corresponds to a first TCI state of the two TCI states, the second value corresponds to a second TCI state of the two TCI states, and the third value corresponds to two TCI states of the two TCI states.

[0148] Embodiment 25 includes the subject matter of embodiment 24, including or omitting optional elements, wherein in response to the field indicating the third value, the one or more processors enable PUCCH repetition for the PUCCH resources configured by the RRC signaling.

[0149] Embodiment 26 includes the subject matter of embodiment 24, including or omitting optional elements, wherein in response to the field indicating the third value, the one or more processors enable PDCCH repeated reception for the CORESET resources configured by the RRC signaling.

[0150] Embodiment 27 includes the subject matter of embodiment 24, including or omitting optional elements, wherein in response to the field encoding the third value, the one or more processors enable a system frame number (SFN) based PDCCH for the CORESET resources configured by the RRC signaling.

[0151] Embodiment 28 is a method for a user equipment (UE), the method comprising: receiving multiple transmission configuration indicator (TCI) states and a unified TCI state activation / deactivation medium access control (MAC) control element (CE) configuration to associate TCI code points in a downlink control information (DCI) format to the TCI states, each TCI code point indicating one or more TCI states; receiving a first single transmission reception point downlink control information (sDCI) including one TCI code point among the multiple TCI code points; receiving a second sDCI scheduled for transmission by a physical uplink shared channel (PUSCH), wherein the second sDCI indicates one or more TCI states among the TCI states associated with the TCI code point of the first sDCI; and in response, sending the PUSCH based on the second sDCI.

[0152] Embodiment 29 includes the subject matter of embodiment 28, including or omitting optional elements, wherein the first sDCI includes a TCI code point among the multiple TCI code points indicating two uplink TCI states including a first TCI state and a second TCI state, wherein the second sDCI includes a field indicating one of at least three values, wherein the first value corresponds to the first TCI state among the two uplink TCI states indicated by the first sDCI, the second value corresponds to the second TCI state among the two uplink TCI states indicated by the first sDCI, and the third value corresponds to both TCI states among the two uplink TCI states indicated by the first sDCI, and the method includes sending the PUSCH transmission based on one or both of the two uplink TCI states indicated by the field of the second sDCI.

[0153] Embodiment 30 includes the subject matter of embodiment 29, including or omitting optional elements, wherein the field corresponds to a dedicated bit of the second sDCI.

[0154] Embodiment 31 includes the subject matter of embodiment 29, including or omitting optional elements, wherein the field is a sounding reference signal (SRS) resource indicator (SRI) field of the second sDCI.

[0155] Embodiment 32 includes the subject matter of embodiment 28, including or omitting optional elements, the subject matter including transmitting the PUSCH based on a spatial domain transmit filter associated with an SRI of a corresponding nearest SRS resource.

[0156] Embodiment 33 includes the subject matter of embodiment 29, including or omitting optional elements, wherein the spatial domain transmit filter used by the nearest SRS resource is configured by radio resource control (RRC) signaling.

[0157] Embodiment 34 is a method comprising any action or combination of actions as substantially described herein in the detailed description.

[0158] Example 35 is a method as substantially described herein with reference to each or any combination of the figures included herein or with reference to each or any combination of the paragraphs in the detailed description.

[0159] Embodiment 36 is a user equipment configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the user equipment.

[0160] Embodiment 37 is a network node configured to perform any action or combination of actions as substantially described herein in a specific embodiment included in the network node.

[0161] Embodiment 38 is a non-transitory computer-readable medium storing instructions that, when executed, cause performance of any action or combination of actions as substantially described herein in the detailed description.

[0162] Embodiment 39 is a device for user equipment, the device comprising a memory and one or more processors, the one or more processors executing instructions stored in the memory so that the UE performs any action or combination of actions substantially described in the specific embodiments herein.

[0163] Embodiment 40 is a device for a network node, the device comprising one or more processors, the one or more processors executing instructions stored in a memory so that the network node performs any action or combination of actions as substantially described in the specific embodiments herein.

[0164] The above description of illustrative examples, implementations, aspects, etc. of the disclosed subject matter, including what is described in the abstract of the specification, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Although specific examples, implementations, aspects, etc. are described herein for illustrative purposes, various modifications can be considered within the scope of such examples, implementations, aspects, etc., as can be appreciated by those skilled in the relevant art.

[0165] Although the method is illustrated above and described as a series of actions or events, it should be understood that the order of such actions or events illustrated should not be interpreted as having a limiting meaning. For example, some actions can occur simultaneously with other actions or events other than those illustrated and / or described herein in different orders. In addition, all the actions shown may not be required to realize one or more aspects or embodiments disclosed herein. In addition, one or more actions in the actions shown herein can be carried out in one or more separate actions and / or stages. In some embodiments, the method shown above can be implemented in a computer-readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the present disclosure protected by the claims.

[0166] The term "coupled" is used throughout the specification. The term can cover connections, communications, or signal paths that enable a functional relationship consistent with the description of the present disclosure. For example, if device A generates a signal to control device B to perform an action, then in the first example, device A is coupled to device B, or in the second example, if the intermediate component C does not substantially change the functional relationship between device A and device B so that device B is controlled by device A via the control signal generated by the device, then device A is coupled to device B through the intermediate component C.

[0167] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A method for a user equipment (UE), the method comprising: receiving a plurality of transmit configuration indicator (TCI) states and a unified TCI state activation / deactivation medium access control (MAC) control element (CE) configuration to associate a plurality of TCI code points in a downlink control information (DCI) format to the TCI states, each TCI code point indicating one or more TCI states; receiving first single transmission reception point downlink control information (sDCI) including one TCI code point among the plurality of TCI code points; receiving a second sDCI scheduled for transmission on a physical uplink shared channel (PUSCH), wherein the second sDCI indicates one or more of the TCI states associated with the TCI code point of the first sDCI; and In response, the PUSCH transmission is sent based on the second sDCI.

2. The method according to claim 1, wherein the first sDCI includes a TCI code point indicating two uplink TCI states including a first TCI state and a second TCI state among the multiple TCI code points, wherein the second sDCI includes a field indicating one of at least three values, wherein the first value corresponds to the first TCI state of the two uplink TCI states indicated by the first sDCI, the second value corresponds to the second TCI state of the two uplink TCI states indicated by the first sDCI, and the third value corresponds to both TCI states of the two uplink TCI states indicated by the first sDCI, and the method includes sending the PUSCH based on one or both of the two uplink TCI states indicated by the field of the second sDCI.

3. The method of claim 2, wherein the field corresponds to a dedicated bit of the second sDCI.

4. The method of claim 2, wherein the field is a Sounding Reference Signal (SRS) Resource Indicator (SRI) field of the second sDCI.

5. The method of claim 1, comprising transmitting the PUSCH based on a spatial domain transmit filter associated with an SRI of a corresponding nearest SRS resource. 6 . The method of claim 5 , wherein the spatial domain transmit filter used by the nearest SRS resource is configured by radio resource control (RRC) signaling.

7. An apparatus for a user equipment (UE), the apparatus comprising one or more processors, the one or more processors configured to cause the UE to: receiving a plurality of transmit configuration indicator (TCI) states and a configuration of a unified TCI state activation / deactivation medium access control (MAC) control element (CE) to associate a plurality of TCI code points of a downlink control information (DCI) format to the TCI states, wherein at least two TCI code points of the plurality of TCI code points are each mapped to two different TCI states; receiving first single downlink control information (sDCI), wherein the first sDCI comprises a TCI code point among the plurality of TCI code points; receiving, at a reception time, a second sDCI that schedules reception of a PDSCH; as well as During a predetermined window after the reception time, one or more TCI states to be adopted for the PDSCH reception are determined based on at least one TCI code point among the multiple TCI code points or the TCI state used to receive the second sDCI.

8. An apparatus according to claim 7, wherein the first sDCI includes a TCI code point among the multiple TCI code points indicating two TCI states including a first TCI state and a second TCI state, and further, wherein the one or more processors are configured to adopt the two TCI states indicated by the TCI code points included in the first sDCI during the predetermined window after the reception time of the second sDCI.

9. The apparatus of claim 7, wherein during the predetermined window after the reception time of the second sDCI, the one or more processors are configured to assume two TCI states indicated by a lowest TCI code point among the multiple TCI code points indicating two TCI states.

10. The apparatus of claim 7, wherein the one or more processors are configured to assume the TCI state for receiving the second sDCI during the predetermined window.

11. The apparatus of claim 10, wherein the TCI state for receiving the second sDCI corresponds to a monitored search space having a lowest control resource set (CORESET) in a latest time slot monitored by the UE.

12. An apparatus according to claim 10, wherein the one or more processors are configured to adopt the TCI state for receiving the second sDCI during the predetermined window when a physical cell identifier (PCI) associated with the two TCI states indicated by the TCI code point included in the sDCI is associated with a neighboring cell that is different from a serving cell of the UE.

13. The apparatus of claim 7, wherein the first sDCI comprises a TCI code point among the plurality of TCI code points indicating two TCI states including a first TCI state and a second TCI state, and further wherein during the predetermined window, the one or more processors are configured to assume one of the two TCI states indicated by the code point included in the first sDCI.

14. The apparatus of claim 7, wherein during the predetermined window, the one or more processors are configured to assume the TCI state having a smallest TCI identifier (ID) of the two TCI states.

15. The apparatus of claim 7, wherein during the predetermined window, the one or more processors are configured to assume the TCI state having the largest TCI ID of the two TCI states.

16. An apparatus according to claim 7, wherein during the predetermined window, the one or more processors are configured to adopt a TCI state of the two TCI states in which a quasi-co-site (QCL) type A / D source reference signal (RS) is configured on a downlink (DL) bandwidth part (BWP) of a serving cell.

17. The apparatus of claim 7, wherein during the predetermined window, the one or more processors are configured to assume one of the two TCI states based on higher layer signaling.

18. A device of a user equipment (UE), the device comprising: Memory; and one or more processors configured to execute instructions stored in the memory so that the UE: receiving a configuration of one or more power control (PC) setting lists, wherein each entry in each of the PC setting lists is associated with one or more transmit receive points (TRPs); receiving a configuration of a plurality of transmit configuration indicator (TCI) code points, each TCI code point indicating one or more activated uplink (UL) TCI states; receiving single transmission reception point downlink control information (sDCI), wherein the sDCI includes a TCI code point of the plurality of TCI code points indicating two UL TCI states, each of the two UL TCI states being associated with one of two different transmission reception points (TRPs); as well as In response to one or both of the two UL TCI states being not associated with a power control setting, sending a PUSCH transmission based on one or more PC settings selected from the corresponding one or more PC setting lists.

19. The apparatus of claim 18, wherein each of the one or more PC setting lists is associated with a different TRP of the two different TRPs.

20. The apparatus of claim 18, wherein every other entry on the single PC settings list is associated with a different TRP of the two different TRPs.

21. An apparatus according to claim 18, wherein the one or more processors are configured to send the PUSCH based on the corresponding PC settings mapped to a PC setting list entry, the PC setting list entry having a lowest index value of the corresponding PC setting list associated with each of the two different TRPs.

22. An apparatus according to claim 18, wherein the one or more processors are configured to send the PUSCH based on the corresponding PC settings mapped to the PC setting list entries identified by the index values ​​of the corresponding PC setting list, wherein the index values ​​are preconfigured by a higher layer for each of the two different TRPs.

23. The apparatus of claim 18, wherein the one or more processors are configured to send the PUSCH based on a PC setting mapped to a PC setting list entry on a PC setting list associated with the two different TRPs.

24. An apparatus according to claim 18, wherein the one or more processors are configured to send the PUSCH based on two PC settings mapped to PC setting list entries, the PC setting list entries having a lowest identifier and a second lowest identifier on the PC setting list associated with the two different TRPs.

25. An apparatus for a user equipment (UE), the apparatus comprising one or more processors, the one or more processors configured to: receiving a plurality of transmit configuration indicator (TCI) states and a unified TCI state activation / deactivation medium access control (MAC) control element (CE) configuration to associate a plurality of TCI code points in a downlink control information (DCI) format to the TCI states, each TCI code point indicating one or more TCI states; receiving first single downlink control information (sDCI), wherein the first sDCI comprises a TCI code point among the plurality of TCI code points; receiving a second sDCI scheduling a PUSCH transmission or a PDSCH reception, wherein the subsequent sDCI does not include a TCI code point; as well as In response to the second sDCI, the PUSCH transmission is sent or the PDSCH reception is received based on a default uplink TCI state or a default downlink TCI state.

26. The apparatus of claim 25, wherein the default uplink TCI state or the default downlink TCI state is hard-coded or predefined by a specification and stored in hardware of the one or more processors of the UE.

27. An apparatus according to claim 26, wherein the first sDCI includes a TCI code point indicating two uplink TCI states or two downlink TCI states among the multiple TCI code points, and further, wherein the default uplink TCI state is predefined in the specification as the first TCI state or the second TCI state among the two uplink TCI states, or the default downlink state is predefined in the specification as the first TCI state or the second TCI state among the two downlink TCI states.

28. An apparatus according to claim 25, wherein the first sDCI includes a TCI code point indicating two uplink TCI states or two downlink TCI states among the multiple TCI code points, and further, wherein the default uplink TCI state or the default downlink TCI state is explicitly configured as the first TCI state or the second TCI state of the two uplink TCI states or the two downlink TCI states through radio resource control (RRC) signaling, medium access control (MAC) control element (CE) or DCI.

29. An apparatus for a user equipment (UE), the apparatus comprising one or more processors, the one or more processors configured to: receiving a plurality of transmit configuration indicator (TCI) states and a configuration of a unified TCI state activation / deactivation medium access control (MAC) control element (CE) to associate a plurality of TCI code points of a downlink control information (DCI) format to the TCI states, wherein at least two TCI code points of the plurality of TCI code points are each mapped to two different TCI states; receiving first single downlink control information (sDCI), wherein the first sDCI includes a TCI code point among the plurality of TCI code points indicating two TCI states including a first TCI state and a second TCI state; receiving, via radio resource control (RRC) signaling, a corresponding configuration for physical uplink control channel (PUCCH) resources or control resource set (CORESET) resources, and an indication of the first TCI state or the second TCI state or both the first TCI state and the second TCI state for the PUCCH resources or the CORESET resources, respectively; and In response, a PUCCH is sent or a PDCCH is received based on the TCI state indicated by the RRC signaling.

30. The apparatus of claim 29, wherein the RRC configuration comprises a field encoding one of at least three values, wherein a first value corresponds to a first TCI state of the two TCI states, a second value corresponds to a second TCI state of the two TCI states, and a third value corresponds to two TCI states of the two TCI states.

31. The apparatus of claim 30, wherein in response to the field indicating the third value, the one or more processors enable PUCCH repetition for the PUCCH resources configured by the RRC signaling.

32. The apparatus of claim 30, wherein in response to the field indicating the third value, the one or more processors enable PDCCH repeated reception for the CORESET resources configured by the RRC signaling.

33. The apparatus of claim 30, wherein in response to the field encoding the third value, the one or more processors enable a system frame number (SFN) based PDCCH for the CORESET resources configured by the RRC signaling.

Images