Integrated TCI framework extension for mTRP-based operation in wireless communication

Abstract

Processes and systems for an integrated transmit configuration indication (TCI) framework extension for multi-transmit / receive point (TRP) operation in wireless communication networks. In the case of an integrated TCI state extension from sTRP to mTRP, the system is configured to support switching between single TRP (sTRP) mode operation and mTRP mode operation. In the case of an integrated TCI state extension from sTRP to mTRP, the system is configured to support up to four TCI states for association with a single TCI code point.

Description

Technical Field

[0001] A wireless communication network provides an integrated communication platform and telecommunications services to wireless user devices. Exemplary telecommunications services include telephony, data (e.g., voice, audio, and / or video data), messaging, and / or other services. The wireless communication network has wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols such as those described in various telecommunications standards published by the Third Generation Partnership Project (3GPP®). Exemplary wireless communication networks include Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal Frequency Division Multiple Access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). The wireless communication network uses technologies such as OFDM, Multiple-Input Multiple-Output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features to facilitate mobile broadband services.

[0002] Overview Fifth Generation (5G) wireless networks support increased connectivity, high capacity, ultra-reliability, and low latency compared to legacy networks. Multiple transmit and receive points (multi-TRP) can improve reliability, coverage, and capacity performance through flexible deployment scenarios. For example, to support the exponential growth of mobile data traffic in 5G and enable coverage expansion, wireless devices access a network composed of mTRP (e.g., macro cells, small cells, pico cells, femto cells, remote radio heads, relay nodes, etc.).

[0003] This document describes the processes and systems for an extension of the Integrated Transmit Configuration Indication (TCI) framework for multi-transmit and receive point (TRP) operation in wireless communication networks. mTRP enables 5G next-generation nodes (gNBs) or other base stations to use two or more transmit / receive points (TRPs) to communicate with user equipment (UEs).

[0004] The TCI framework is extended to mTRP use cases based on an extension of the integrated TCI framework to represent multiple DL and uplink (UL) TCI states. Specifically, the process is extended to multi-TRP use cases. In the case of the integrated TCI state extension from sTRP to mTRP, the system is configured to support switching between single TRP (sTRP) mode operation and mTRP mode operation.

[0005] In the case of an integrated TCI state extension from sTRP to mTRP, the system is configured to support up to four TCI states for association with a single TCI code point, rather than two TCI states. Specifically, for TCI code points associated with fewer than four TCI states, the system is configured to indicate or determine that each activated joint / DL / UL TCI state corresponds to a first or second joint / DL / UL TCI state within the full set of TCI states. Furthermore, this document describes how to efficiently support CC group-based TCI state indication for component carriers (CCs) with mixed sTRP and mTRP modes.

[0006] According to one aspect of the present disclosure, an exemplary process includes a user device (UE) receiving configuration data from a wireless communication network, the TCI field being a field describing one or more transmit configuration indicator (TCI) states for at least one cell of the communication network. The process includes the UE selecting a transmit / receive point (TRP) mode for the UE, such that the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode, according to the configuration data. The process includes the UE transmitting data to a cell of the wireless communication network, which is also operating in TRP mode, based on the selected TRP mode.

[0007] In some implementations, configuration data specifies a first number of TCI states for uplink transmission and a second number of TCI states for downlink transmission. In some implementations, the UE is configured to select sTRP mode when the first and second numbers of TCI states indicated in the configuration data are integer values ​​less than 2. In some implementations, the UE is configured to select mTRP mode when the first or second number of TCI states indicated in the configuration data contains an integer value greater than 1. In some implementations, the TCI mode is explicitly specified in the TCI field of the Downlink Control Information (DCI) format. In some implementations, the configuration data includes a logical cell identifier (eLCID), and the TRP mode is based on the value of the eLCID. In some implementations, the configuration data is contained within a Media Access Control (MAC) control element (CE), and the MAC CE includes multiple fields, which specify a set of TCI states associated with a TCI code point. In some implementations, the first field value of a field among multiple fields indicates the first pair of TCI states in the full TCI state set, and the second field value of a field among multiple fields indicates the second pair of TCI states in the set of TCI states. In some implementations, the MAC subheader of the MAC CE specifies the eLCID that indicates the cell associated with the set of TCI states. In some implementations, the UE is configured to update the TCI state for the cell associated with the TCI code point indicated in the MAC CE, and the UE maintains other TCI states for the cell associated with the TCI code point that are not updated in the MAC CE. In some implementations, the configuration data is part of the Radio Resource Control (RRC) signaling, and the TCI field indicates the TCI state for the TCI code point for updating by the UE. In some implementations, the RRC signaling includes a downlink / uplink identifier field and a pair identifier field.

[0008] According to one aspect of the present disclosure, an exemplary process includes a user device (UE) receiving configuration data comprising a component carrier (CC) list for a cell group, wherein the CC list specifies a reference cell and one or more transmit configuration indicator (TCI) states specifying for the reference cell, and other cells in the CC list are configured to use one or more TCI states specified for the reference cell. The process includes the UE selecting a transmit / receive point (TRP) mode for the UE according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode. The process includes the UE transmitting data to cells in a radio communication network that also operate in TRP mode, based on the selected TRP mode.

[0009] In some implementations, the CC list includes one or more sTRP CCs and one or more sDCI-based mTRP CCs. In some implementations, the reference cell consists of sDCI-based mTRP CCs, and radio resource control (RRC) signaling specifies that a first group, a second group, or both groups of TCI states for the reference cell are used for the sTRP.

[0010] In some implementations, the CC list includes one or more sTRP CCs and one or more mDCI-based mTRP CCs. In some implementations, the reference cell consists of sDCI-based mTRP CCs, and radio resource control (RRC) signaling specifies a CORESET pool index value. In some implementations, the CC list includes one or more sDCI-based mTRP CCs and one or more mDCI-based mTRP CCs. In some implementations, one of the CCs with sDCI-based mTRPs is designated as the reference CC. In some implementations, one of the CCs with mDCI-based mTRPs is designated as the reference CC. In some implementations, the first TCI state of the sDCI-based mTRP is mapped to a designated TCI state specific to the first CORSET pool index value.

[0011] Details of one or more embodiments of these systems and methods are described in the accompanying drawings and the following description. Other features, subjects, and advantages of these systems and methods will become apparent from the description and drawings, as well as the claims. [Brief explanation of the drawing]

[0012] [Figure 1] This shows several implementations of wireless networks.

[0013] [Figure 2] This shows an example of a network configured to switch between single TRP mode (sTRP) and multi-TRP mode (mTRP).

[0014] [Figure 3] An example of a full set of TCI state combinations for joint TCI state modes and separate TCI state modes is shown.

[0015] [Figure 4] An example of a media access control (MAC) control element (CE) for updating the TCI status is shown.

[0016] [Figure 5A] An example of radio resource control (RRC)-based TCI state update indication for single downlink control information (sDCI)-based multi-TRP is shown. [Figure 5B] An example of radio resource control (RRC)-based TCI state update indication for single downlink control information (sDCI)-based multi-TRP is shown.

[0017] [Figure 6] An example of cell group-based TCI state where the CC list includes both sTRP-based mTRP operation and sDCI-based mTRP operation is shown.

[0018] [Figure 7] Flowcharts of exemplary methods according to some implementations are shown.

[0019] [Figure 8] Flowcharts of exemplary methods according to some implementations are shown.

[0020] [Figure 9] Exemplary user equipment (UE) according to some implementations is shown.

[0021] [Figure 10] Exemplary access nodes according to some implementations are shown.

Mode for Carrying Out the Invention

[0022] This document describes the processes and systems for an integrated transmit configuration indication (TCI) framework extension for multi-transmit and receive point (TRP) operation in wireless communication networks. mTRP enables a 5G next-generation node (gNB) or other base station to use two or more transmit / receive points (TRPs) to communicate with user equipment (UE). Beam management in 5G downlink (DL) includes a TCI signaling framework in which the beam for a target or channel / signal (e.g., PDSCH, PDCCH, CSI-RS) to be received by the UE is indicated by TCI states. TCI states are transmitted dynamically in downlink control information (DCI) messages. Downlink control information (DCI) messages include configurations such as pseudo-collocation (QCL) relationships between a downlink (DL) reference signal (RS) and a physical downlink shared channel (PDSCH) demodulation reference signal (DMRS) port in a single set of control state information reference signals (CSI-RS). The integrated TCI framework enables streamlined multi-beam operation for frequency range 2 (FR2). More specifically, each link direction (UL, DL) follows a single TCI state, such as analog beams for all channels, streamlining beam management. This document describes the extension from single TRP (sTRP) use cases to an integrated TCI framework focusing on multi-TRP (mTRP) use cases.

[0023] The TCI framework is extended to mTRP use cases based on an extension of the integrated TCI framework to represent multiple DL and uplink (UL) TCI states. Specifically, the process is extended to multi-TRP use cases. In the case of the integrated TCI state extension from sTRP to mTRP, the system is configured to support switching between single TRP (sTRP) mode operation and mTRP mode operation. The difference between these modes is the number of TCI states supported (e.g., multiple states instead of one). For example, each TRP in an mTRP (e.g., two TRPs) may be associated with multiple TCI states. Explicit indications from the network to the UE may be provided for configured mTRPs to avoid mismatches between the network and the UE, such as mismatches between the transmit and receive beams of the UE and the network.

[0024] In the case of an integrated TCI state extension from sTRP to mTRP, the system is configured to support up to four TCI states for association with a single TCI code point, rather than two TCI states. Specifically, for TCI code points associated with fewer than four TCI states (e.g., N=2 with {DL TCI state=3, UL TCI state=2}), the system is configured to indicate or determine that each activated joint / DL / UL TCI state corresponds to the first or second joint / DL / UL TCI state in the full set of TCI states. For added flexibility, when the UE is moving, all fewer than four TCI states may need to be updated. For example, only three TCI states (or fewer) may be updated. The UE can indicate to the network how it updated the TCI states.

[0025] This document describes how to efficiently support CC group-based TCI state indication for component carriers (CCs) having mixed sTRP and mTRP modes. In legacy systems, the base cell TCI state is updated, and each cell in the cell group has a corresponding updated TCI state. The process described herein allows component carriers in a cell group to have different TRP configurations than the base cell. For example, the base cell may be configured in sTRP mode. A second cell in the cell group may be configured in mTRP mode with a single DCI-based mTRP. A third cell in the cell group may be configured in mTRP mode with multiple DCI-based mTRPs. Group-based TCI updates can still be used for cell groups. Using group-based TCI updates reduces signal overhead between the UE and the network. Group-based TCI updates reduce memory consumption overhead for the UE because the UE does not need to store TCI states for multiple CCs in the cell group.

[0026] Figure 1 shows several implementations of the wireless network 100. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and base station 104 communicate using a system that supports control for managing the UE 102's access to the network via base station 104.

[0027] In some implementations, the wireless network 100 may be a non-standalone (NSA) network incorporating Long-Term Evolution (LTE) and 5G New Radio (NR) communication standards as defined by the 3G Partnership Project (3GPP®) technical specifications. For example, the wireless network 100 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR dual connectivity (EN-DC) network, or an NR-EUTRA dual connectivity (NE-DC) network. In some other implementations, the wireless network 100 may be a standalone (SA) network incorporating only 5G NR. Furthermore, other types of communication standards are possible, including future 3GPP® systems (e.g., 6th generation (6G)), IEEE 802.11 technologies (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11-2007, IEEE 802.11n, IEEE 802.11-2012, IEEE 802.11ac, or other currently or future-developed IEEE 802.11 technologies), and IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.). While aspects may be described herein using terms generally related to 5G NR, aspects of this disclosure may apply to other systems, such as systems following 3G, 4G, and / or 5G (e.g., 6G).

[0028] In the wireless network 100, UE 102 and any other UEs in the system may be, for example, machine-type devices such as laptop computers, smartphones, tablet computers, smart meters or dedicated devices for healthcare, intelligent transport systems, or any other wireless devices. In the network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via an air interface 108 within the base station service area provided by base station 104. In some implementations, such a wider network may be a wide-area network operated by a cellular network provider, or it may be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area may be divided into multiple sectors associated with one or more specific antennas. Such sectors may be physically associated with one or more fixed antennas and may be assigned to physical areas using one or more adjustable tunable antennas or antenna configurations in a beamforming process used to direct signals to specific sectors.

[0029] UE102 includes a control circuit 110 coupled to a transmitter circuit 112 and a receiver circuit 114. Each of the transmitter circuit 112 and the receiver circuit 114 may be coupled to one or more antennas. The control circuit 110 may include various combinations of application-specific circuits and baseband circuits. The transmitter circuit 112 and the receiver circuit 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuits and / or front-end module (FEM) circuits.

[0030] In various implementations, the transmitter circuit 112, the receiver circuit 114, and the control circuit 110 may be integrated in various ways to implement the operations described herein. The control circuit 110 may be adapted or configured to perform various operations, such as those described elsewhere in this disclosure relating to the UE.

[0031] The transmitting circuit 112 can perform various operations as described herein. Furthermore, the transmitting circuit 112 may transmit using multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed, for example, by time division multiplexing (TDM) or frequency division multiplexing (FDM) together with carrier aggregation. The transmitting circuit 112 may be configured to receive block data from the control circuit 110 for transmission via the air interface 108.

[0032] The receiving circuit 114 can perform various operations as described herein. Furthermore, the receiving circuit 114 may receive multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuit 110. The multiple downlink physical channels may be multiplexed, for example, by TDM or FDM along with carrier aggregation. The transmitting circuit 112 and the receiving circuit 114 can transmit and receive both structured control data and content data (e.g., messages, images, videos, etc.) within data blocks carried by the physical channels, respectively.

[0033] Figure 1 also shows base station 104. In some implementations, base station 104 may be a 5G radio access network (RAN), next-generation RAN, E-UTRAN, non-terrestrial cell, or legacy RAN such as UTRAN. As used herein, terms such as "5G RAN" may refer to base station 104 operating on an NR or 5G radio network 100, and terms such as "E-UTRAN" may refer to base station 104 operating on an LTE or 4G radio network 100. UE 102 utilizes connections (or channels) 106A, 106B, each including a physical communication interface or layer.

[0034] The base station 104 circuit may include a control circuit 116 coupled to a transmit circuit 118 and a receive circuit 120. Each of the transmit circuit 118 and the receive circuit 120 may be coupled to one or more antennas that can be used to enable communication via the air interface 108. Each of the transmit circuit 118 and the receive circuit 120 may be adapted to transmit and receive data to and from any UE connected to the base station 104. The receive circuit 120 may receive multiple uplink physical channels from one or more UEs, including UE 102.

[0035] In Figure 1, one or more channels 106A, 106B are shown as air interfaces enabling communicable coupling and may conform to cellular communication protocols such as UMTS protocol, 3GPP® LTE protocol, Advanced Long-Term Evolution (LTE-A) protocol, LTE-Based Access to Unlicensed Spectrum (LTE-U), 5G protocol, NR protocol, NR-Based Access to Unlicensed Spectrum (NR-U) protocol, and / or any other communication protocol(s). In implementations, UE102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as the sidelink (SL) interface and may include, but is not limited to, one or more logical channels, including a physical sidelink control channel (PSCCH), a physical sidelink discovery link channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0036] Figure 2 shows an example of a network 200 configured to switch between single TRP mode (sTRP) and multi-TRP (mTRP) mode. Specifically, examples of network signaling to explicitly or implicitly indicate to the UE that it should switch between sTRP and mTRP are described.

[0037] DCI formats 1_1 or 1_2 may include a TCI field indicating whether sTRP mode or mTRP mode is used for a TCI state(s). In one example, the network explicitly configures either sDCI-based "sTRP" mode or sDCI-based "mTRP" mode using RRC. RRC signaling causes the UE to update the TCI state based on the TCI field in the DCI format. In another example, the switchover is based on the contents of a Rel-18 TCI state activation / deactivation command.

[0038] The UE determines, based on several different conditions, that the "Rel-18 sDCI-based mTRP" operation is used to update the integrated TCI state. For example, in joint TCI mode, at least one TCI code point is associated with two joint TCI states based on the activation command. Code points in MAC CE are numeric entries in a table that map to a specific entity (e.g., a node). The UE can determine that the base station (gNB)'s TCI mode is mTRP mode without explicit signaling from the network. The UE can configure four TCI states on its side. In separate DL and UL TCI modes, at least one TCI code point may be associated with two DL TCI states or two UL TCI states. The UE can determine that the base station (gNB) is operating in mTRP mode without explicit signaling from the network.

[0039] Figure 2 shows the data within the Media Access Control (MAC) control element (CE) 202. For each TCI code point value, the MAC CE indicates a set of DL TCI states and a set of UL TCI states from the base station to the UE. For TCI code point 0, only one TCI state is specified for each of the DL TCI state and UL TCI state. Specifically, for code point 0, the DL TCI state is {1} and the UL TCI state is {2}, and for code point 1, the DL TCI state is {3} and the UL TCI state is {1}. The UE can determine that the base station is operating in sTRP mode. For MAC CE 204, for each TCI code point 0, 1, two or more TCI states are indicated for either the DL TCI state or the UL TCI state. For example, for TCI code point 0, the DL TCI state is {1,6}, which is two or more TCI states. The UE can determine that the base station is operating in mTRP mode. Similarly, for TCI code point 1, MAC CE 204 specifies multiple UL TCI states {1,8}. Without explicit signaling, the UE can determine that the network is operating in mTRP mode after MAC CE 204 is received. Although both TCI code points 0 and 1 indicate two or more TCI states, the UE can determine that the network is operating in mTRP mode based on either TCI code point 0 or 1, which individually contains two or more TCI states for UL or DL. In each of the examples in Figure 2, a single MAC CE 202 or MAC CE 204 is received by the UE.

[0040] In another example, the dedicated logical cell identifier (eLCID) is a MAC subheader indicating a Rel-18 activation / deactivation command. If a Rel-18 activation / deactivation command is detected based on the value of the dedicated eLCID, the UE can determine that MAC CE 202 or MAC CE 204 represents a Rel-18 mTRP operation (rather than a Rel-17 sTRP operation). The UE can use the eLCID to determine that the network is operating in mTRP mode even if only one TCI state is indicated for each of the UL and DL TCI state information in MAC CE 202, 204.

[0041] A UE can consist of a set of control resource sets (CORESETs). A CORESET is a set of physical resources (e.g., a specific area in a DL resource grid) and a set of parameters used to carry PDCCH / DCI. In this example, each CORESET is associated with one of two modes by RRC signaling. The UE updates the TCI state according to the mode value associated with the CORESET in which the DCI was detected.

[0042] Figure 3 shows an example of a full set (e.g., four states) of TCI state combinations 300 for joint TCI state modes and separate TCI state modes. The combination includes a first pair 302 and a second pair 304. Each pair of TCI states 302, 304 includes UL TCI states and DL TCI states. The full set of TCI state combinations 300 is associated with a TCI code point (e.g., MAC CE 202 or 204 in Figure 2). MAC-CE is configured for TCI state activation / deactivation for sDCI-based mTRP operation, as previously described. To enable TCI state update description, the TCI states associated with a single TCI code point are labeled as shown in Figure 3, covering both joint TCI state modes and separate TCI state modes. MAC CE is further described in relation to Figure 4. For both the MAC CE and RRC approaches, the signaling indicates whether a "first" pair 302 or a "second" pair 304 of TCI states has been updated. The first pair 302 includes the first UL and first DL TCI states. The second pair 304 includes the second UL TCI state and the second DL TCI state. The first and second indicators allow the MAC CE or RRC signaling to specify a subset (<4) of TCI states that has been updated, as described above.

[0043] Figure 4 shows an example of a media access control (MAC) control element (CE) 400 for updating the TCI status. The MAC-CE 400 may include the following fields, as shown in Figure 4: Field U i This indicates that either the first (e.g., pair 302) TCI state or the second (e.g., pair 304) TCI state in the integrated TCI state is updated by the indicated TCI state "i+1". i The field is set to "0" to indicate that TCI state "i" is being used to update the first TCI state. iThe field is set to "1" to indicate that TCI state "i" is being used to update the second TCI state. The MAC-CE 400 is identified by a MAC subheader with a dedicated eLCID, as illustrated in relation to Figure 2. The UE updates the TCI state indicated by the TCI code point and maintains other TCI states that are not updated by the TCI code point. Each octet is an indicator for DL / UL communication, and U i It includes a TCI state identifier consisting of fields. In the example in Figure 4, TCI state ID 2 is associated with U1. If the U1 field is set to 0, the UE determines that the "first" pair 302 of TCI states has been updated. Depending on the U / D indicator (for example, in octet 5), the UE can determine which of the four TCI states in the full set 300 should be updated. In this example, when the UE operates in mTRP mode, all TCI states are updated as needed for operation, and a subset of TCI states may be updated, or the full set may be updated by the UE.

[0044] Figures 5A and 5B illustrate an example of radio resource control (RRC)-based TCI state update indication for single downlink control information (sDCI)-based multi-TRP. The network can use RRC signaling to inform the UE of updated TCI states. For each joint / DL / UL-TCI state, the network uses RRC signaling to indicate which TCI states within the full set of TCI state combinations (e.g., combination 300) should be updated by it. The UE shall update the TCI states indicated by the TCI code points and maintain other TCI states that are not updated by the TCI code points.

[0045] Figure 5A shows an exemplary TCI state update indication information element (IE) 500 containing eight TCI states configured by RRC signaling. The eight states include four DL TCI states and four UL TCI states. For each TCI state, the RRC signaling specifies either a “first” value or a “second” value to indicate the relevant TCI state in the full set for update. The RRC configuration is updated with a new information element specifying either the first or second state. MAC CE 400 is sent more frequently than the RRC message shown in Figure 5A.

[0046] Figure 5B shows an example of the current full set of TCI states 510 maintained by the UE. The current full set of TCI states 510 includes TCI states {1, 1, 2, and 2}. When the UE receives a TCI code point associated with TCI states 3 / 4, the UE updates the full set 510 to the updated set of TCI states 520. The UE updates the second DL TCI state with TCI state #3 and the first UL TCI state in the full set 510 with TCI state #4. The UE updates the full set of TCI states 510 to the updated set of TCI states 520, which includes {4, 1, 3, and 2}. As shown in Figure 5A, TCI-IDs 3 and 4 are updated in the information element 500. TCI-ID 3 is DL in the second set. TCI-ID 4 is UL in the first set. As shown in Figure 5B, the set of TCI states 510 is updated to the updated set of TCI states 520. The TCI-ID in the second set for UL (TCI states 530) is updated to TCI-ID=3. The TCI-ID in the first set for DL ​​(TCI states 540) is updated to TCI-ID=4, as specified in the RRC information element 500 in Figure 5A.

[0047] Figure 6 shows an exemplary environment 600 in which the CC list includes cell group-based TCI states that include both sTRP-based mTRP behavior and sDCI-based mTRP behavior. Various approaches can be considered to operate cell group-based TCI state indication using the “simultaneousTCI-UpdateList” parameter. In the first example, the CC list configured by “simultaneousTCI-UpdateList” includes a mixture of sTRP CCs (single or multiple) and sDCI-based mTRP CCs (single or multiple). The UE expects the base CC to consist of sDCI-based mTRP CCs. There are two TCI states indicated by the sDCI mTRP. For each sTRP CC, RRC signaling is used to indicate that the “first,” “second,” or “both” indicated TCI states on the base CC are used for the sTRP. In another example, the CC list configured by “simultaneousTCI-UpdateList” includes a mixture of sTRP CCs (single or multiple) and mDCI-based MTRP CCs (single or multiple). The baseline CC uses mDCI mTRP. The UE expects that the baseline CC will consist of mDCI-based mTRP CCs, not sDCI-based mTRP CCs. For each sTRP CC, RRC signaling is used to indicate that one of the following is used for sTRP: The indicated TCI state is specific to “coresetPoolIndex=0”. The indicated TCI state is specific to “coresetPoolIndex=1”. The indicated TCI state is specific to “coresetPoolIndex=0”, and the TCI state is specific to “coresetPoolIndex=1”. Figure 6 shows an exemplary environment 600 with cell group-based TCI states, and the CC list includes both sTRP and sDCI-based mTRP behavior.

[0048] The CC list 610, comprised of "simultaneousTCI-UpdateList", includes a mixture of sDCI-based mTRP and mDCI-based MTRP CCs (one or more). The network can support the following reference CC configurations: A first configuration (configuration #1) specifies that one of the CCs with sDCI-based mTRP is designated as the reference CC. A second configuration (configuration #2) specifies that one of the CCs with mDCI-based mTRP is designated as the reference CC. Network 600 is shown, and its CCs #1, #2, #3, #4, and #5 are shown in List 610. UE 602 operates in mTRP and communicates with serving cell 604 and non-serving cell 606. Each of CCs #2-5 operates in sTRP with UE 602. CCs #2 and #3 are the first pair, and CCs #4 and #5 are the second pair. The TCI status of multiple cells can be updated with a single message specifying the update list in List 610. Updating multiple CCs with a single message reduces messaging overhead between UE 602 and network 600.

[0049] Several approaches can be considered for TCI state indication. In the first option, the rules are hard-coded in the specification. The first TCI state of an sDCI-based mTRP is mapped to a specified TCI state specific to "coresetPoolIndex=0". Conversely, if an mDCI-based mTRP is a reference CC, "coresetPoolIndex=0" can update the first TCI state of other CCs in the group. The second TCI state of an sDCI-based mTRP is mapped to a specified TCI state specific to "coresetPoolIndex=1". Conversely, if an mDCI-based mTRP is a reference CC, "coresetPoolIndex=1" can update the second TCI state of other CCs in the group. In the second option, RRC signaling is used to indicate which of the two TCI states on the reference CC is used. In the first configuration, the "first" or "second" TCI state is configured to update the TCI state specific to "coresetPoolIndex=0" and the TCI state specific to "coresetPoolIndex=1" on the sDCI-based mTRP CC, and vice versa (as described above). In the second configuration, the TCI state specific to "coresetPoolIndex=0" or specific to "coresetPoolIndex=1" is used to update the "first" or "second" TCI state on the mDCI-based mTRP CC, and vice versa (as described above).

[0050] Figures 7 and 8 show flowcharts of exemplary individual methods 700 and 800 in several implementation forms, respectively. For clarity of presentation, the following description generally explains methods 700 and 800 in the context of other figures in this description. For example, methods 700 and 800 can be performed by UE102 in Figure 1. It will be understood that methods 700 and 800 can be performed, as needed, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware. In some implementation forms, the various steps of methods 700 and 800 can be performed in parallel, in combination, in loops, or in any order.

[0051] Figure 7 shows an exemplary process 700. Process 700 includes the user equipment (UE) receiving configuration data from a radio communication network, which includes TCI fields describing one or more transmit configuration indicator (TCI) states for at least one cell of the communication network (702). Process 700 includes the UE selecting a transmit / receive point (TRP) mode for the UE according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode (704). Process 700 also includes the UE transmitting data to a cell of the radio communication network, which is also operating in TRP mode, based on the selected TRP mode (706).

[0052] In some implementations, configuration data specifies a first number of TCI states for uplink transmission and a second number of TCI states for downlink transmission. In some implementations, the UE is configured to select sTRP mode when the first and second numbers of TCI states indicated in the configuration data are integer values ​​less than 2. In some implementations, the UE is configured to select mTRP mode when the first or second number of TCI states indicated in the configuration data contains an integer value greater than 1. In some implementations, the TCI mode is explicitly specified in the TCI field of the Downlink Control Information (DCI) format. In some implementations, the configuration data includes a logical cell identifier (eLCID), and the TRP mode is based on the value of the eLCID. In some implementations, the configuration data is contained within a Media Access Control (MAC) control element (CE), and the MAC CE includes multiple fields, which specify a set of TCI states associated with a TCI code point. In some implementations, the first field value of a field among multiple fields indicates the first pair of TCI states in the full TCI state set, and the second field value of a field among multiple fields indicates the second pair of TCI states in the set of TCI states. In some implementations, the MAC subheader of the MAC CE specifies the eLCID that indicates the cell associated with the set of TCI states. In some implementations, the UE is configured to update the TCI state for the cell associated with the TCI code point indicated in the MAC CE, and the UE maintains other TCI states for the cell associated with the TCI code point that are not updated in the MAC CE. In some implementations, the configuration data is part of the Radio Resource Control (RRC) signaling, and the TCI field indicates the TCI state for the TCI code point for updating by the UE. In some implementations, the RRC signaling includes a downlink / uplink identifier field and a pair identifier field.

[0053] Figure 8 shows an exemplary process 800. Process 800 includes the user equipment (UE) receiving configuration data (802) which includes a component carrier (CC) list for a cell group, wherein the CC list specifies a reference cell and one or more transmit configuration indicator (TCI) states for the reference cell, and the other cells in the CC list are configured to use one or more TCI states specified for the reference cell. Process 800 includes the UE selecting a transmit / receive point (TRP) mode for the UE according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode (804). Process 800 also includes the UE transmitting data (806) to cells in a radio communication network that are also operating in TRP mode, based on the selected TRP mode.

[0054] In some implementations, the CC list includes one or more sTRP CCs and one or more sDCI-based mTRP CCs. In some implementations, the reference cell consists of sDCI-based mTRP CCs, and the Radio Resource Control (RRC) signaling specifies that a first group, a second group, or both groups of TCI states for the reference cell are used for the sTRP.

[0055] In some implementations, the CC list includes one or more sTRP CCs and one or more mDCI-based mTRP CCs. In some implementations, the reference cell consists of sDCI-based mTRP CCs, and radio resource control (RRC) signaling specifies a CORESET pool index value. In some implementations, the CC list includes one or more sDCI-based mTRP CCs and one or more mDCI-based mTRP CCs. In some implementations, one of the CCs with sDCI-based mTRPs is designated as the reference CC. In some implementations, one of the CCs with mDCI-based mTRPs is designated as the reference CC. In some implementations, the first TCI state of the sDCI-based mTRP is mapped to a designated TCI state specific to the first CORSET pool index value.

[0056] The exemplary methods 700 and 800 shown in Figures 7 and 8 may be modified or reconfigured to include additional, fewer, or different steps (not shown in Figure 7 or 8), which may be performed in the order shown or in a different order.

[0057] Figure 9 shows exemplary UE1000 in several implementation configurations. The UE1000 may be similar to the UE102 in Figure 1 and may be substantially interchangeable.

[0058] The UE1000 can be any mobile or non-mobile computing device, such as mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, volt / current meters, etc.), video devices (e.g., cameras, video cameras, etc.), wearable devices (e.g., smartwatches), or relaxed-IoT devices.

[0059] The UE1000 may include a processor 1002, an RF interface circuit 1004, memory / storage 1006, a user interface 1008, a sensor 1010, a driver circuit 1012, a power management integrated circuit (PMIC) 1014, one or more antennas 1016, and a battery 1018. The components of the UE1000 may be implemented as an integrated circuit (IC), a part thereof, a separate electronic device or other module, logic, hardware, software, firmware, or a combination thereof. The block diagram in Figure 9 is intended to show a high-level diagram of some of the components of the UE1000. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the components shown may be used in other implementations.

[0060] The components of the UE1000 may be coupled with various other components via one or more interconnectors 1020, and one or more interconnectors may represent any kind of interface, input / output section, (local, system, or expansion) bus, transmission line, trace, optical connection, etc., which can cause various circuit components (on common or different chips or chipsets) to interact with each other.

[0061] The processor 1002 may include, for example, a baseband processor circuit (BB) 1022A, a central processing unit circuit (CPU) 1022B, and a graphics processing unit circuit (GPU) 1022C. The processor 1002 may include any type of circuit or processor circuit that executes or otherwise operates computer executable instructions, such as program code, software modules, or functional processes, from the memory / storage 1006, to cause the UE 1000 to perform the operations described herein.

[0062] In some implementations, the baseband processor circuit 1022A can access the communication protocol stack 1024 in the memory / storage 1006 to communicate over a 3GPP®-compliant network. Generally, the baseband processor circuit 1022A can access the communication protocol stack to perform user plane functions in the physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptive protocol (SDAP) layer, and PDU layer, and control plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some implementations, the operation of the PHY layer may be additionally / alternatively performed by components of the RF interface circuit 1004. The baseband processor circuit 1022A can generate or process baseband signals or waveforms that carry information within a 3GPP®-compliant network. In some implementations, the waveform for noise reduction (NR) can be based on cyclic prefix quadrature frequency division multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and discrete Fourier transform spread OFDM "DFT-S-OFDM" in the uplink.

[0063] The memory / storage 1006 may include one or more non-temporary computer-readable media (e.g., a communication protocol stack 1024) containing instructions that can be executed by one or more processors 1002 to cause the UE 1000 to perform the various operations described herein. The memory / storage 1006 includes any type of volatile or non-volatile memory that can be distributed throughout the UE 1000. In some implementations, some of the memory / storage 1006 may reside on the processor 1002 itself (e.g., L1 and L2 caches), while other memory / storage 1006 may be outside the processor 1002 but accessible via memory interfaces. The memory / storage 1006 may include, but is not limited to, any suitable volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0064] The RF interface circuit 1004 may include a transceiver circuit and a radio frequency front module (RFEM) that enable the UE 1000 to communicate with other devices via a radio access network. The RF interface circuit 1004 may include various elements located in the transmit or receive path. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, and the like.

[0065] In the receiving path, the RFEM receives the radiated signal from the air interface via antenna(s) 1016, and subsequently filters and amplifies the signal (using a low-noise amplifier). The signal may also be provided to the receiver of the transceiver, which downconverts the RF signal to a baseband signal, and the baseband signal is provided to the baseband processor of processor 1002.

[0066] In the transmission path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal using a power amplifier before the signal is radiated across the air interface via the antenna(s) 1016. In various implementations, the RF interface circuit 1004 may be configured to transmit and receive signals in a manner compliant with NR access technology.

[0067] Antenna(s) 1016 may include one or more antenna elements for converting electrical signals into radio waves so that they can travel through the air, and for converting received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. Antenna(s) 1016 may have antenna panels that are omnidirectional, directional, or a combination thereof, enabling beamforming and multi-input multi-output communication. Antenna(s) 1016 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna(s) 1016 may have one or more panels designed for a specific frequency band, including the FR1 or FR2 band.

[0068] The user interface circuit 1008 includes various input / output (I / O) devices designed to enable user interaction with the UE1000. The user interface 1008 includes input device circuits and output device circuits. The input device circuit includes, among other things, any physical or virtual means for receiving input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, and so on. The output device circuit includes any physical or virtual means for displaying information, such as sensor readings, actuator positions (one or more), or other similar information, or for conveying information in other ways. The output device circuit may include any number or combination of audio or visual displays, in particular one or more simple visual outputs / indicators (e.g., binary state indicators such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.). Outputs such as characters, graphics, and multimedia objects are generated or created from the operation of the UE1000.

[0069] Sensor 1010 may include devices, modules, or subsystems intended to detect events or changes in its environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers; micro-electromechanical systems or nano-electromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless apertures); light detection and distance measurement sensors; proximity sensors (e.g., infrared detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices.

[0070] The driver circuit 1012 may include software and hardware elements that operate to control specific devices that are incorporated into the UE1000, attached to the UE1000, or otherwise coupled to the UE1000 in a communicative manner. The driver circuit 1012 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE1000. For example, the driver circuit 1012 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface, a sensor driver for acquiring sensor readings from sensor 1010 and controlling and allowing access to sensor 1010, a driver for acquiring the actuator position of an electromechanical component or for controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0071] The PMIC1014 can manage the power supplied to various components of the UE1000. In particular, with respect to the processor 1002, the PMIC1014 can control power supply selection, voltage scaling, battery charging, or DC-DC conversion.

[0072] In some implementations, the PMIC 1014 can control or otherwise be part of the various power-saving mechanisms of the UE 1000. The battery 1018 may power the UE 1000, but in some examples, the UE 1000 may be mounted and deployed in a fixed location and may have a power source coupled to a power distribution network. The battery 1018 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery. In some implementations, such as vehicle-based applications, the battery 1018 may be a typical automotive lead-acid battery.

[0073] Figure 10 shows exemplary access node 1100 (e.g., base station or gNB) in several implementation configurations. Access node 1100 is similar to base station 104 and may be substantially interchangeable. Access node 1100 may include a processor 1102, RF interface circuitry 1104, core network (CN) interface circuitry 1106, memory / storage circuitry 1108, and one or more antennas 1110.

[0074] The components of the access node 1100 may be coupled with various other components via one or more interconnectors 1112. The processor 1102, RF interface circuit configuration 1104, memory / storage circuit configuration 1108 (including the communication protocol stack 1114), antenna(s) 1110 and interconnectors 1112 may be similar to elements with similar names shown and described with respect to Figure 9. For example, the processor 1102 may include processor circuits such as a baseband processor circuit (BB) 1116A, a central processing unit (CPU) 1116B and a graphics processing unit (GPU) 1116C.

[0075] The CN interface circuit 1106 may provide connectivity to a core network, such as a 5th Generation Core network (5GC), using a 5GC-compliant network interface protocol, such as the Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to and from the access node 1100 via optical fiber or wireless backhaul. The CN interface circuit 1106 may include one or more dedicated processors or FPGAs for communication using one or more of the protocols described above. In some implementations, the CN interface circuit 1106 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0076] As used herein, terms such as “access node” and “access point” may describe equipment that provides wireless baseband functionality for data connectivity and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). As used herein, terms such as “NG RAN node” may refer to an access node 1100 operating on an NR or 5G system (e.g., gNB), and terms such as “E-UTRAN node” may refer to an access node 1100 operating on an LTE or 4G system (e.g., eNB). Depending on the implementation, the access node 1100 may be implemented as one or more dedicated physical devices, such as a macrocell base station and / or a low-power (LP) base station to provide a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0077] In some implementations, all or part of the access node 1100 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be called CRAN and / or virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 1100 may be or may operate as a “roadside unit”. The term “roadside unit” or “RSU” may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, and an RSU implemented in or by a UE may be called a “UE-type RSU”, an RSU implemented in or by an eNB may be called an “eNB-type RSU”, an RSU implemented in or by a gNB may be called a “gNB-type RSU”, and so on.

[0078] For convenience, various components may be described in this specification as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to perform.” Descriptions of components configured to perform one or more tasks are expressly intended not to be subject to the interpretation of § 112(f) of the U.S. Patent Act.

[0079] For one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, or methods as described in the following Examples section. For example, the baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the embodiments described below. As another example, a circuit associated with a UE, base station, network element, etc., as described above in relation to one or more of the aforementioned figures, may be configured to operate according to one or more of the embodiments described below in the Examples section.

[0080] Any of the embodiments described above may be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementations are illustrative and illustrative, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible based on the above teachings or can be learned from the practice of various embodiments.

[0081] Although the embodiments described above are described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art if the above disclosure is fully understood. The following claims are intended to be construed as encompassing all such variations and modifications.

[0082] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

Claims

1. It is a method, In a user device (UE), configuration data is received from a wireless communication network, including a TCI field that describes one or more Transmit Configuration Indicator (TCI) states for at least one cell of the communication network. The UE selects a TRP mode according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode. The aforementioned UE transmits data to the cells of the wireless communication network, which are also operating in the aforementioned TRP mode, based on the selected TRP mode. Methods that include...

2. The method according to claim 1, wherein the configuration data specifies a first number of TCI states for uplink transmission and a second number of TCI states for downlink transmission.

3. The method according to claim 2, wherein the UE is configured to select the sTRP mode when the first number of TCI states and the second number of TCI states shown in the configuration data are each integer values ​​less than 2.

4. The method according to claim 2, wherein the UE is configured to select the mTRP mode when the first number of TCI states or the second number of TCI states shown in the configuration data is an integer value greater than 1.

5. The method according to claim 1, wherein the TCI mode is explicitly specified in the TCI field of the Downlink Control Information (DCI) format.

6. The method according to claim 1, wherein the configuration data includes a logical cell identifier (eLCID), and the TRP mode is based on the value of the eLCID.

7. The method according to claim 1, wherein the configuration data is included in a media access control (MAC) control element (CE), the MAC CE includes a plurality of fields, the plurality of fields specifying a set of TCI states associated with a TCI code point.

8. The method according to claim 7, wherein the first field value of one of the plurality of fields indicates a first pair of TCI states in the full TCI state set, and the second field value of one of the plurality of fields indicates a second pair of TCI states in the set of TCI states.

9. The method according to claim 7, wherein the MAC subheader of the MAC CE specifies an eLCID indicating a cell associated with the set of TCI states.

10. The method according to claim 7, wherein the UE is configured to update the TCI state for the cell associated with the TCI code point shown in the MAC CE, and the UE maintains other TCI states for the cell associated with the TCI code point that are not updated in the MAC CE.

11. The method according to claim 1, wherein the configuration data is part of a radio resource control (RRC) signaling, and the TCI field indicates the TCI state for a TCI code point for updating by the UE.

12. The method according to claim 11, wherein the RRC signaling includes a downlink / uplink identifier field and a pair identification field.

13. It is a method, In a user device (UE), receiving configuration data including a component carrier (CC) list for a cell group, wherein the CC list specifies a reference cell and one or more Transmit Configuration Indicator (TCI) states for the reference cell, and other cells in the CC list are configured to use the one or more TCI states specified for the reference cell; The UE selects a TRP mode according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode. A method comprising transmitting data to a cell of the wireless communication network, which is also operating in the TRP mode, based on the selected TRP mode, using the aforementioned UE.

14. The method according to claim 13, wherein the CC list includes one or more sTRP CCs and one or more sDCI-based mTRP CCs.

15. The method according to claim 14, wherein the reference cell is comprised of an sDCI-based mTRP CC, and the radio resource control (RRC) signaling specifies that a first group, a second group, or both groups of TCI states for the reference cell are used for the sTRP.

16. The method according to claim 13, wherein the CC list includes one or more sTRP CCs and one or more mDCI-based mTRP CCs.

17. The method according to claim 16, wherein the reference cell is composed of an sDCI-based mTRP CC, and radio resource control (RRC) signaling specifies a value for the CORESET pool index.

18. The method according to claim 13, wherein the CC list includes one or more sDCI-based mTRP CCs and one or more mDCI-based mTRP CCs.

19. The method according to claim 18, wherein one of the CCs having an sDCI-based mTRP is shown as the reference CC.

20. The method according to claim 18, wherein one of the CCs having an mDCI-based mTRP is shown as the reference CC.

21. The method according to claim 18, wherein a first TCI state of an sDCI-based mTRP is mapped to the indicated TCI state specific to a first CORSET pool index value.

22. The method according to claim 21, wherein a second TCI state of an sDCI-based mTRP is mapped to the indicated TCI state which is specific to a second CORSET pool index value different from the first CORSET pool index value.

23. The method according to claim 18, wherein RRC signaling specifies the TCI state for the reference cell.

24. A system comprising one or more computers and one or more storage devices which store instructions that, when executed by the one or more computers, are operable to cause the one or more computers to perform an operation according to any one of claims 1 to 23.

25. A non-temporary computer storage medium, which, when executed by one or more computers, is encoded with instructions that cause the one or more computers to perform an operation according to any one of claims 1 to 23.

26. A processor of a user device (UE) configured to perform an operation, wherein the operation is In a user device (UE), configuration data is received from a wireless communication network, including a TCI field that describes one or more Transmit Configuration Indicator (TCI) states for at least one cell of the communication network. The UE selects a TRP mode according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode. A processor comprising transmitting data to a cell of the wireless communication network, which is also operating in the TRP mode, based on the selected TRP mode, via the UE.

27. A processor of a user device (UE) configured to perform an operation, wherein the operation is In a user device (UE), receiving configuration data including a component carrier (CC) list for a cell group, wherein the CC list specifies a reference cell and one or more Transmit Configuration Indicator (TCI) states for the reference cell, and other cells in the CC list are configured to use the one or more TCI states specified for the reference cell; The UE selects a TRP mode according to the configuration data, wherein the TRP mode is either a single TRP (sTRP) mode or a multi-TRP (mTRP) mode. A processor comprising transmitting data to a cell of the wireless communication network, which is also operating in the TRP mode, based on the selected TRP mode, via the UE.

Images