Techniques for transmit configuration indicator association for physical downlink shared channel reception

Abstract

The application relates to devices and components, including apparatuses, systems, and methods for transmit configuration indicator association for physical downlink shared channel reception.

Description

Technical Field

[0001] The present application generally relates to communication networks and, more particularly, to techniques related to transmission configuration indicator association for physical downlink shared channel reception. Background Art

[0002] A user equipment (UE) may be connected to a network via multiple transmit / receive points (TRPs). In multi-TRP (mTRP) transmission, different TRPs may provide different data or the same data for spatial multiplexing to improve robustness. Multi-TRP can be supported by a single downlink control information (DCI) mode and a multi-DCI mode. In the single DCI (sDCI) mode, one TRP transmits DCI to schedule PDSCH transmissions from more than one TRP. In the multi-DCI (mDCI) mode, TRPs can independently schedule their own PDSCHs. Brief Description of the Drawings

[0003] Figure 1 Illustrates a network environment according to some embodiments.

[0004] Figure 2 Illustrates a code point setting according to some embodiments.

[0005] Figure 3 Illustrates a medium access control (MAC) control element (CE) according to some embodiments.

[0006] Figure 4 Illustrates a pair of transmission configuration indicator (TCI) state lists and DCI according to some embodiments.

[0007] Figure 5 Illustrates another pair of TCI state lists and DCI according to some embodiments.

[0008] Figure 6 Illustrates another pair of TCI state lists and DCI according to some embodiments.

[0009] Figure 7 Illustrates DCI according to some embodiments.

[0010] Figure 8 Illustrates an example operation for updating a TCI state according to some embodiments.

[0011] Figure 9 Illustrates another exemplary operation for updating a TCI state according to some embodiments.

[0012] Figure 10 Illustrates a signaling diagram according to some embodiments.

[0013] Figure 11 Illustrates an operation flow / algorithm structure according to some embodiments.

[0014] Figure 12 Is another operation flow / algorithm structure according to some embodiments.

[0015] Figure 13 Illustrates another operation flow / algorithm structure according to some embodiments.

[0016] Figure 14 Illustrates a user equipment according to some embodiments.

[0017] Figure 15 Illustrates a network node according to some embodiments. Detailed Description

[0018] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, and / or technologies, in order to provide a thorough understanding of various aspects of some embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects may be practiced in other examples without these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various aspects with unnecessary detail. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B); and the phrase “based on A” means “at least partially based on A,” e.g., it may be “based only on A” or it may be “partially based on A.”

[0019] The following is a glossary of terms that may be used in the present disclosure.

[0020] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or group), or memories (shared, dedicated, or group) configured to provide the described functionality, application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable system on a chip (SoC)), and / or digital signal processors (DSPs). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functionality of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of the hardware elements and the program code may be referred to as a particular type of circuit.

[0021] As used herein, the term "processor circuit" refers to, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or a circuit for recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device, software module, or functional process capable of executing or otherwise operating on computer-executable instructions (such as program code).

[0022] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0023] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities and that can represent a remote user of network resources in a communication network. Additionally, the term "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0024] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of computers communicatively coupled to each other. Further, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems communicatively coupled to each other and configured to share computing resources or networking resources.

[0025] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computing device, a mechanical device, a memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and applications or workload units, etc. "Hardware resources" may refer to computing, storage, or networking resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or networking resources provided by a virtualization infrastructure to applications, devices, systems, etc. The term "network resource" or "communication resource" may refer to resources accessible to a computing device / system via a communication network. The term "system resource" may refer to any kind of shared entity that provides services and may include computing resources or networking resources. System resources may be regarded as a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and can be clearly identified.

[0026] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to convey data or a data stream. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", or any other similar term indicating a path or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection made between two devices for sending and receiving information.

[0027] As used herein, the terms "instantiate", "instantiation", etc. refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0028] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other via a communication channel, link, interface, or reference point.

[0029] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networked hardware, network equipment, network node, virtualized network function, etc.

[0030] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element containing content. An information element may include one or more additional information elements.

[0031] As used herein, the term "plurality" means more than one.

[0032] Figure 1 Network environment 100 is illustrated according to some embodiments. Network environment 100 may include a UE 104 and a base station (BS) 108. The base station 108 may provide one or more radio access cells, e.g., a 3rd Generation Partnership Project (3GPP) New Radio (NR) cell, through which the UE 104 may communicate with the base station 108. The UE 104 and the base station 108 may communicate via an air interface compatible with 3GPP technical specifications, such as those defining the system standards for 5th Generation (5G) NR or higher generations.

[0033] The base station 108 may include a controller 112 coupled to one or more TRPs, e.g., TRP 116 and TRP 120. Generally, the controller 112 may perform most operations of the communication protocol stack, including scheduling, while the TRPs 116 and 120 act as distributed antennas. In some embodiments, the TRPs 116 and 120 may perform some low-layer operations of the communication protocol stack (e.g., analog Physical (PHY) layer operations). Although Figure 1 the TRPs 116 and 120 are shown as part of the base station 108, in other embodiments, the TRPs 116 and 120 may be associated with different base stations.

[0034] The base station 108 may use the TRPs 116 and 122 to geographically separate the points from which signals may be sent to or received from the UE 104. This may increase the flexibility of using multiple-input multiple-output (MIMO) and beamforming enhancements to communicate with the UE 104. The TRPs 116 and 120 may be used to transmit the same or different downlink transmissions to the UE 104. In some embodiments, the distributed transmission / reception capabilities provided by the TRPs 116 and 120 may be used in a coordinated multi-point or carrier aggregation system.

[0035] In the sDCI mode, DCI transmitted by a single TRP (e.g., TRP 116) can schedule the transmission of physical downlink shared channels (PDSCHs) from multiple TRPs (e.g., TRP 116 and TRP 120). The DCI can schedule PDSCH transmission by indicating the PDSCH transmission occasion in which the PDSCH can be transmitted. As Figure 1 shown, in the corresponding PDSCH transmission occasion, TRP 116 will transmit the first PDSCH transmission (PDSCH 1), and TRP 120 will transmit the second PDSCH transmission (PDSCH 2). In various embodiments, PDSCH 1 and PDSCH 2 may include the same or different information.

[0036] Transmissions using different antenna ports may experience different radio channels. However, in some cases, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler drift, Doppler spread, average delay, delay spread, or spatial reception parameters (e.g., characteristics associated with the angle of arrival of the downlink received signal at the UE). Antenna ports that share one or more of these large-scale radio channel characteristics may be referred to as being quasi-co-located with each other. 3GPP has defined four types of quasi-co-location (QCL) to indicate which specific channel characteristics are shared. In QCL type A, the antenna ports share Doppler drift, Doppler spread, average delay, and delay spread. In QCL type B, the antenna ports share Doppler drift, and Doppler spread is shared. In QCL type C, the antenna ports share Doppler drift and average delay. In QCL type, the antenna ports share spatial receiver parameters.

[0037] The base station 108 can provide transmission configuration indicator (TCI) state information to the UE 104 to indicate the QCL relationship between the antenna ports for reference signals (e.g., synchronization signal / physical broadcast channel (PBCH) or channel state information reference signal (CSI-RS)) and downlink data or control signaling (e.g., PDSCH or physical downlink control channel (PDCCH)). The base station 108 can use a combination of radio resource control (RRC) signaling, MAC CE signaling, and DCI to notify the UE 104 of these QCL relationships.

[0038] Initially, the base station 108 may configure multiple TCI states for the UE 104 via RRC signaling. In some embodiments, up to 128 TCI states may be configured for the PDSCH via, for example, the PDSCH-config information element, and up to 64 TCI states may be configured for the PDCCH via, for example, the PDCCH-config information element. Each TCI state may include an indication of a cell identifier, a bandwidth part identifier, a relevant SS / PBCH block or CSI-RS, and an indication of a QCL type. After the initial configuration, the TCI states may be set to inactive.

[0039] Then, the base station 108 may send an activation command via, for example, a MAC CE. The activation command may activate up to eight combinations of TCI states, which eight combinations correspond to eight code points of the TCI code point field in the DCI. Then one or more specific TCI states may be dynamically selected and signaled using the TCI code point field in the DCI to indicate which of the active TCI states are applicable to the PDSCH resource allocation.

[0040] The initial state framework of Release 15 of 3GPP stipulates that the TCI states are indicated separately for different DL channels (e.g., PDSCH and PDCCH), which may enable different DL channels to use different active TCI states. Although this provides significant flexibility, it is also associated with a relatively large signaling overhead. Release 17 of 3GPP has developed a unified TCI framework to facilitate simplified multi-beam operation for higher frequency ranges (e.g., frequency range 2 (FR2) from 24,250 megahertz (MHz) to 71,000 MHz). With the unified TCI, a single active TCI state may be used as the unified downlink TCI state to be applied to all PDSCH / PDCCH channels. A unified uplink TCI state may also be defined / applied to uplink channels (e.g., physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH)).

[0041] The unified TCI framework of Release 17 focuses on the sTRP use case. It may be beneficial to extend the unified TCI framework to the mTRP use case. To accommodate the unified TCI framework for mTRP, up to four TCI states may be indicated in a CC / bandwidth part (BWP) or a CC / BWP set in a component carrier (CC) list. In the case of MAC CE-based activation of TCI states, up to four TCI states that may be used for DL reception or UL transmission may be indicated / updated by the MAC CE or the DCI.

[0042] Embodiments of the present disclosure solve various problems to ensure flexibility in the unified TCI state indication for mTRP.

[0043] In the first problem, the embodiment describes how to indicate TCI state updates through DCI formats for two TRPs. For example, the TCI code point field in DCI can include three bits, which support eight combinations of TCI states, and each combination is associated with a code point in the TCI code point field. Each combination can include up to four TCI states. For example, TCI state #1, TCI state #2, TCI state #3, and TCI state #4. Therefore, up to 8 * 8 * 8 * 8 = 4096 combinations will be needed to support up to eight candidates with full flexibility. This will require 12-bit indication. The embodiment describes how to use a 3-bit TCI code point field to efficiently update 4,096 combinations of TCI states for mTRP (e.g., two TRPs).

[0044] In the second problem, the embodiment describes how to associate two downlink TCI states indicated by the TCI code point with PDSCH reception in sDCI mTRP.

[0045] Various aspects for indicating up to four unified TCI states for sDCI mTRP operation can be considered.

[0046] In the first aspect, each TCI code point in DCI can always be associated with four TCI states. Figure 2 An example code point setting 200 according to the first aspect is illustrated. The code point setting 200 can include eight code points, which can be indicated by a 3-bit TCI code point field in DCI. Each of these eight code points can be associated with a different combination of four TCI states. The four TCI states of the code point can correspond to two uplink TCI states and two downlink TCI states. For example, these four TCI states can respectively correspond to DL state #1 (e.g., the TCI state that UE 104 will use to receive downlink transmissions from TRP #1), UL state #1 (e.g., the TCI state that UE 104 will use to send uplink transmissions to TRP #1), DL state #2 (e.g., the TCI state that UE 104 will use to receive downlink transmissions from TRP #2), and UL state #2 (e.g., the TCI state that UE 104 will use to send uplink transmissions to TRP #2). Therefore, if UE 104 receives DCI with a TCI code point field set to "101", it will indicate code point 5. Then, UE 104 can determine that it will use TCI state #7, TCI state #3, TCI state #8, and TCI state #10 for DL state #1, UL state #1, DL state #2, and UL state #2 respectively.

[0047] The second aspect of providing unified TCI state indication for sDCI mTRP may rely on a TRP-specific active TCI state list. In the second aspect, MAC CE can be used for TRP-specific TCI state activation, followed by unified TCI state indication for multiple TRPs.

[0048] Figure 3 Illustrated is a MAC CE 300 that can be used to activate / deactivate a TCI state in a TRP-specific TCI state list according to some embodiments.

[0049] In the first octet, the MAC CE 300 may include a 1-bit field to indicate a list identifier (ID) that provides an indication of whether the MAC CE 300 is applicable to a first TCI state list or a second TCI state list. In some embodiments, this list ID may be referred to by other names, such as virtual ID, set ID, TRP ID, etc.

[0050] The first octet may also include a 5-bit field for the serving cell ID and a 2-bit field for the DL BWP ID to indicate the identities of the serving cell and the DL BWP to which the MAC CE is applicable, respectively.

[0051] In the second octet, the MAC CE 300 may include multiple reserved fields labeled "R" and may include a 2-bit field for the UL BWP ID to indicate the identity of the UL BWP to which the MAC CE is applicable.

[0052] The P i field in the third octet can be used to indicate whether each TCI code point has multiple TCI states or a single TCI state. For example, if the P 2 field is set to 1, the second TCI code point includes multiple TCI states.

[0053] Octets 4 to octet N+3 respectively configure TCI state ID 1 to TCI state ID N. The D / U field can be used to indicate whether the TCI state ID in the same octet is for a combined / downlink TCI state or an uplink TCI state. If this field is set to 1, the TCI state ID is for combined / downlink.

[0054] By using a MAC CE with a list ID (such as MAC CE 300), up to two lists can be created. If additional bits are used for the list ID, more lists can be created. Each element in the list can include a TCI state for combined / downlink state, UL state, or both.

[0055] Figure 4Illustrated is a pair of TCI state lists 400 and DCI 404 that can be used in a unified TCI state indication for multiple TRPs. The pair of TCI state lists 400 can include a first TCI state list 408 and a second TCI state list 412.

[0056] The first TCI state list 408 can include eight sets of TCI states respectively corresponding to eight TCI code points. Each set of TCI states can include one or more TCI states. The eight sets of TCI states in the first TCI state list

[0057] 408 can be activated by a MAC CE having a first list ID (e.g., list ID = 0).

[0058] Similarly, the second TCI state list 412 can include eight sets of TCI states respectively corresponding to eight TCI code points. The eight sets of TCI states in the second TCI state list 408 can be activated by a MAC CE having a second list ID (e.g., list ID = 1). In some embodiments, the first TCI state list 408 can correspond to a first TRP (e.g., TRP 116), while the second TCI state list corresponds to a second TRP (e.g., TRP 120).

[0059] The DCI 404 can include two 3-bit TCI code point fields, multiple other fields, and a cyclic redundancy check (CRC) field. The first 3-bit TCI code point field can correspond to the first TCI state list 408 (e.g., list ID = 0). For example, the first 3-bit TCI code point field can be set with a value "101" to indicate that the set of TCI states of the fifth TCI code point will be used as the unified TCI state for the first TRP. The second 3-bit TCI code point field can correspond to the second TCI state list 412 (e.g., list

[0060] ID = 1). For example, the second 3-bit TCI code point field can be set with a value "001" to indicate the second

[0061] set of TCI states of the TCI code point will be used as the unified TCI state for the second TRP.

[0062] In some designs, to avoid increasing the DCI size, the use of the two 3-bit TCI code point fields (as shown in DCI 404) can be restricted to DCI format 1_1 / DCI format 1_2 in the case where there is no data scheduling. This can be done by reusing a previously reserved field of DCI format 1_1 / DCI format 1_2 as the second TCI code point field.

[0063] Figure 5Illustrated is a pair of TCI state lists 500 and DCI 504 that can be used in a unified TCI state indication for multiple TRPs. The pair of TCI state lists 500 may include a first TCI state list 508 and a second TCI state list 512.

[0064] The first TCI state list 508 and the second TCI state list 512 can be activated in a manner similar to that discussed above with respect to Figure 3 and Figure 4 discussed.

[0065] DCI 504 may include a 1-bit list ID field, a 3-bit TCI code point field, multiple other fields, and a CRC field. The 1-bit list ID field can be used to indicate whether the TCI state indicated by the TCI code point field is applicable to the first TCI state list 508 or the second TCI state list 512. For example, if the 1-bit list ID field is set to "0" and the TCI code point field is set to "101", the UE 104 can determine that the fifth TCI code point will be used as the unified TCI state for only the first TRP. Conversely, if the 1-bit list ID field is set to "1" and the TCI code point field is set to "101", the UE 104 can determine that the fifth TCI code point will be used as the unified TCI state for only the second TRP.

[0066] Figure 6 Illustrated is a pair of TCI state lists 600 and DCI 604 that can be used in a unified TCI state indication for multiple TRPs. The pair of TCI state lists 600 may include a first TCI state list 608 and a second TCI state list 612.

[0067] The first TCI state list 608 and the second TCI state list 612 can be activated in a manner similar to that discussed above with respect to Figure 3 and Figure 4 discussed.

[0068] DCI 604 may include a 2-bit list ID field, a 3-bit TCI code point field, multiple other fields, and a CRC field. The 2-bit list ID field can be used to indicate whether the TCI state indicated by the TCI code point field is applicable to the first TCI state list 508 or the second TCI state list 512. For example, the first bit (b 0 ) of the 2-bit list ID field can be set to indicate whether the TCI state indicated by the TCI code point field is applicable to the first TRP, and the second bit (b 0 ) of the 2-bit list ID field can be set to indicate whether the TCI state indicated by the TCI code point field is applicable to the second TRP. If b iis set to “1”, the indicated TCI state applies to the corresponding TRP, and if b i is set to “0”, the indicated TCI state does not apply to the corresponding TRP. For example, if the TCI code point field is set to “101”, and b 0 and b 1 are both set to “1”, then UE104 can determine that TCI 0,5 applies to the first TRP and TCI 1,5 applies to the second TRP.

[0069] Figure 7 Illustrates DCI 700 that utilizes bitmap-based TCI state application indication according to some embodiments. In some embodiments, DCI 700 may have DCI format 1_1 / DCI format 1_2 in the presence or absence of scheduling.

[0070] The maximum number of TCI states that can be associated with a TCI code point by activating / deactivating the MAC CE can be M. In some embodiments, M = 4. When four TCI states are associated with a TCI code point, they may correspond to DL / UL TCI state 704. For example, these four TCI states may correspond to DL state #1, UL state #1, DL state #2, and UL state #2, respectively.

[0071] DCI 700 may include an application field, a TCI code point field, one or more other fields, and a CRC field. The application field may include a bitmap to provide an indication of whether the TCI state indicated by the TCI code point field applies to each of the DL / UL TCI states 704. Each bit of the bitmap may be associated with the TCI state indicated by the TCI code point field. For example, if M = 4 and the application field includes a 4-bit bitmap “b 0 b 1 b 2 b 3 ”, then each of these bits may be mapped one-to-one with each of the four TCI states to indicate whether the TCI state indicated by the TCI code point field is updated. If b i = 0, the associated TCI state is not applied. If b i = 1, the associated TCI state is applied.

[0072] Figure 8 Illustrates an example operation 800 for updating TCI states according to bitmap-based TCI state indication according to some embodiments. In the first time period T1, UE 104 may be configured with DL TCI state #4, UL TCI state #2, DL TCI state #6, and UL TCI state #3.

[0073] As part of operation 800, UE 104 may receive DCI (e.g., DCI 700) that has an application field set to "1101" and a TCI code point value indicating TCI code points for TCI state #8, TCI state #4, TCI state #2, and TCI state #0. Based on the value of the application field, UE 104 may determine to update the first TCI state, the second TCI state, and the fourth TCI state based on the TCI states indicated by the TCI code points. For example, UE 104 may update the first DL TCI state to TCI state #8, the first UL TCI state to TCI state #4, and the second UL TCI state to TCI state #0 based on the indicated corresponding TCI states. However, since the b 2 bit is set to "0", the second DL TCI state may not be updated and that TCI state may remain in its state at T1 (e.g., TCI state #6). Thus, operation 800 may result in a combination of set TCI states (e.g., #8, #4, #6, and #0) that may not even be associated with one TCI code point.

[0074] While the above example corresponds to the case where a TCI code point is associated with four TCI states, in other embodiments, when a TCI code point is associated with fewer than four TCI states, the application field may also be used to update the TCI states. For example, if a TCI code point is associated with only one TCI state (e.g., TCI state #9) and the bitmap of the application field includes the value 1101, UE 104 may update DL state #1, UL state #1, and UL state #2 to TCI state #9 and may keep DL state #2 unchanged.

[0075] In some embodiments, when creating a TRP-specific activation list by a MAC CE as described with respect to Figure 3 , Figure 4 , Figure 5 and Figure 6 , the use of a bitmap-based TCI state application indication as shown and described with respect to Figure 7 may be applied.

[0076] In some embodiments, a 2-bit application field may be used in DCI format 1_1 / DCI format 1_2 to provide a bitmap-based TCI state application indication. In these embodiments, the first bit b 0 of the application field may be used to indicate whether to apply a first set of one or more TCI states, while the second bit b 1 of the application field may be used to indicate whether to apply a second set of one or more TCI states. If b i= 0, the TCI state may not be applied, and if b i = 1, the TCI state may be applied.

[0077] In some embodiments, the mapping of the 2-bit application field to the indicated TCI state may be provided by Table 1 or Table 2 below.

[0078] Bits within the application field Indicated TCI state <![CDATA[b 0 > First and third (e.g., odd indices) <![CDATA[b 1 > Second and fourth (e.g., even indices)

[0079] Table 1

[0080] Bits within the application field Indicated TCI state <![CDATA[b 0 > First and second (e.g., first consecutive set indices) <![CDATA[b 1 > Third and fourth (e.g., second consecutive set indices)

[0081] Table 2

[0082] Although both Table 1 and Table 2 map the two indicated TCI states to each bit of the application field, in other embodiments, other mappings may be used. For example, the first bit may be mapped to the first indicated state, while the second bit is mapped to the last three indicated states.

[0083] Figure 9 Illustrates an example operation 900 for updating the TCI state according to some embodiments in accordance with bitmap-based TCI state indication. Specifically, operation 900 may correspond to using a two-bit application field and a mapping corresponding to Table 1.

[0084] During a first time period T1, UE 104 may be configured with DL TCI state #4, UL TCI state #2, DL TCI state #6, and UL TCI state #3.

[0085] As part of operation 900, UE 104 may receive DCI that has a 2-bit application field set to "10" and a TCI code point value indicating TCI code points with TCI state #8, TCI state #4, TCI state #2, and TCI state #0. Based on the value of the application field and referring to Table 1, UE 104 may determine to update the first TCI state and the third TCI state based on the TCI states indicated by the TCI code points. For example, UE 104 may update the first DL TCI state to TCI state #8 and the second DL TCI state to TCI state #2. However, since the b 1 bit is set to "0", UE 104 may determine that the second and fourth TCI states will not be updated, and those TCI states may maintain their states at T1 (e.g., TCI state #2 and TCI state #3).

[0086] Another aspect of the present disclosure may provide for the TCI association of PDSCH with sDCI-based mTRP. Assuming that two unified combined / DL TCI states are indicated by TCI code points in DCI formats, multiple signaling methods may be considered for sDCI-based mTRP to determine the applied TCI state. The following four options describe some signaling methods. Some of these options may be used together with other options. For example, they are not mutually exclusive.

[0087] In a first option, an RRC parameter may explicitly indicate which of the two indicated TCI states will be used for PDSCH reception. For example, the RRC parameter may indicate that the first TCI state will be used for PDSCH reception, the second TCI state will be used for PDSCH reception, or both the first TCI state and the second TCI state will be used for PDSCH reception. The RRC parameter may be provided in each control resource set (CORESET) configuration or in each PDSCH configuration. The RRC parameter may configure the TCI state to be used based on each bandwidth part (BWP).

[0088] A second option may correspond to a case where the time offset between the scheduling DCI and the first symbol of the scheduled PDSCH is less than a predetermined threshold window. This predetermined threshold window may be referred to as timeDurationForQCL of QCL, which may correspond to the amount of time required for the UE to decode the DCI and possibly return the RF circuit based on the TCI state indicated by the DCI before receiving the PDSCH based on the updated TCI state. In some embodiments, the UE 104 may provide an indication of the value of timeDurationForQCL to the base station 108 as part of the UE capability report. This may be provided based on each subcarrier spacing (SCS).

[0089] Figure 10 FIG. 1000 is a signaling diagram illustrating timeDurationForQCL according to some embodiments. Signaling diagram 1000 includes a first DCI (DCI#1) scheduling a first PDSCH transmission (PDSCH#1) and a second DCI (DCI#2) scheduling a second PDSCH transmission (PDSCH#2). The timeDurationForQCL window may start after the last symbol of the PDCCH used for transmitting the DCI.

[0090] As shown in the figure, PDSCH#1 is received within the timeDurationForQCL window after DCI#1. According to the second option, UE 104 can determine the default TCI state that the UE can use to receive PDSCH#1 based on a fixed rule (e.g., the first TCI state or the second TCI state is always used as the default TCI state) or based on the first option (e.g., RRC parameters according to the CORESET configuration / PDSCH configuration).

[0091] In some embodiments of the second option, the default TCI state can be the QCL assumption of the lowest CORESETID in the most recently monitored time slot. In the case of carrier aggregation (CA), the lowest CC index can be selected. In this way, the last TCI state used to monitor the PDCCH before receiving the PDSCH can also be used as the default TCI state for PDSCH transmission.

[0092] In the case where the gap between the scheduled DCI and the scheduled PDSCH transmission is greater than timeDurationForQCL, UE104 can use the TCI state indicated by the TCI code point field to receive the PDSCH transmission.

[0093] In some embodiments, the base station 108 can provide an instruction to UE 104 regarding whether UE 104 uses the first option or the second option, for example, via RRC signaling. Additionally / alternatively, one of these options (the first option or the second option) can be defined as the default mode and applied unless another option is explicitly configured.

[0094] In the third option, UE 104 can assume that the TCI state indicated by the TCI code point field in the scheduled DCI will be applied to the PDSCH transmission received after a timeDurationForQCL duration starting from the end symbol of the PDCCH carrying the DCI. Refer to Figure 10 , consider that the TCI code point field in DCI#1 indicates TCI state #2. As discussed above, DCI#1 schedules PDSCH#1; however, PDSCH#1 is within the timeDurationForQCL window. Therefore, UE 104 cannot apply TCI state #2 to PDSCH#1. However, UE 104 can still update its receive beam based on TCI state #2. In this way, TCI state #2 can be applied to the PDSCH transmission received after the timeDurationForQCL window, for example, PDSCH#2 (in the case where PDSCH#2 is received within the timeDurationForQCL window of DCI#2 and UE 104 cannot use any TCI state indicated in DCI#2).

[0095] In a fourth option, the TCI state indicated by the TCI code point in the DCI format can be applied as a default beam for PDSCH transmission within a timeDurationForQCL duration starting from the end symbol of the PDCCH carrying the DCI.

[0096] Figure 11 An operation flow / algorithm structure 1100 according to some embodiments is shown. The operation flow / algorithm structure 1100 can be implemented by a UE (e.g., UE 104) or 1400 or components therein (e.g., the processor 1404).

[0097] The operation flow / algorithm structure 1100 can include: at 1104, receiving information associating eight TCI code points with respective combinations of four TCI states. In some embodiments, the configuration information can be received in a MAC CE for activating / deactivating a TCI state associated with a specific TCI code point sent from a base station.

[0098] In some embodiments, the four TCI states can correspond to a first DL TCI state associated with a first TRP, a first UL TCI state associated with the first TRP, a second DL TCI state associated with a second TRP, and a second UL TCI state associated with the second TRP. These TCI states can be unified states. For example, the first DL TCI state can be used for both PDSCH transmission and PDCCH transmission from the first TRP, the first UL TCI state can be used for both PUSCH and PUCCH transmission to the first TRP, and so on.

[0099] The operation flow / algorithm structure 1100 can further include: at 1108, receiving a DCI having a 3-bit value in a TCI code point field to indicate a first TCI code point.

[0100] The operation flow / algorithm structure 1100 can further include: at 1112, processing uplink transmission or downlink transmission based on one or more TCI states associated with the first TCI code point. Specifically, the UE can adjust its transmission beam or reception beam based on the one or more TCI states.

[0101] In some embodiments, the DCI may include an application field to provide additional indication of which TCI states will be used to update the configuration of the UE. For example, the application field may be a 4-bit field including a bitmap that provides an indication of whether each of the four TCI states will be used to update the corresponding TCI state of the UE. As another example, the application field may be a 2-bit field, where each of these bits provides an indication of whether one or more associated TCI updates will be used to update the corresponding TCI state of the UE. For example, the association of the bits with the corresponding TCI states may be consistent with the mappings of Table 1 and Table 2.

[0102] Figure 12 is an operation flow / algorithm structure 1200 according to some embodiments. The operation flow / algorithm structure 1200 may be implemented by a base station (such as, for example, base station 108) or a network node 1500 or components therein (e.g., processor 1504).

[0103] The operation flow / algorithm structure 1200 may include: at 1204, sending a first MAC CE having a first list ID and a first TCI state ID to configure a first TCI state list. The first list ID may be a 1-bit value indicating whether the list corresponds to the first TRP or the second TRP.

[0104] The operation flow / algorithm structure 1200 may further include: at 1208, sending a second MAC CE having a second list ID and a second TCI state ID to configure a second TCI state list. The second list ID may be a 1-bit value indicating whether the list corresponds to the first TRP or the second TRP to supplement the first ID list.

[0105] After the first TCI state list and the second TCI state list are configured, the base station may then use DCI having TCI code point values corresponding to one or more of these lists to indicate a specific TCI state. In some embodiments, the DCI may include multiple TCI code point fields. In other embodiments, the DCI may include one TCI code point field and additional information indicating whether the TCI code point field corresponds to the first list, the second list, or both the first list and the second list.

[0106] Figure 13 is an operation flow / algorithm structure 1300 according to some embodiments. The operation flow / algorithm structure 1300 may be implemented by a UE (e.g., UE 104 or 1400) or components therein (e.g., processor 1404).

[0107] The operation flow / algorithm structure 1300 may include: at 1304, identifying two unified TCI states associated with a TCI code point.

[0108] The operation flow / algorithm structure 1300 may further include: at 1308, determining that one or both of the two unified TCI states will be used as the default TCI state. In some embodiments, the determination at 1308 may be based on RRC parameters in the CORESET configuration / PDSCH configuration, which provide an explicit indication of which TCI state or states will be used as the default TCI state. In other embodiments, the default TCI state may be set to the TCI state used by the UE to monitor PDCCH transmissions. In still other embodiments, the default TCI state for the first PDSCH transmission may be set to the TCI state indicated in the DCI for scheduling the second PDSCH transmission, which occurs before the first PDSCH transmission.

[0109] The operation flow / algorithm structure 1300 may further include: at 1312, receiving a PDSCH transmission based on the default TCI state. In some embodiments, when the time offset between the scheduling DCI and the scheduled PDSCH transmission is less than timeDurationforQCL, the default TCI state may be used for the PDSCH transmission. In other embodiments, the default TCI state may be used for PDSCH transmissions that are not specifically scheduled by a DCI (e.g., semi-persistent scheduled PDSCH transmissions) or for PDSCH transmissions scheduled by a DCI that does not include a TCI code point value.

[0110] Figure 14 Illustrated is a UE 1400 according to some embodiments. The UE 1400 may be similar to Figure 1 the UE 104 and may be substantially interchangeable therewith.

[0111] The UE 1400 may be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smartwatch), or an Internet of Things device.

[0112] The UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage device 1412, a user interface 1416, sensors 1420, a drive circuit 1422, a power management integrated circuit (PMIC) 1424, an antenna structure 1426, and a battery 1428. The components of the UE 1400 may be implemented as integrated circuits (ICs), parts of integrated circuits, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or combinations thereof.Figure 14 The block diagram is intended to show a high-level view of some of the components of UE 1400. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the shown components may occur in other specific implementations.

[0113] The components of UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, or optical connector that allows various circuit components (on common or different chips or chip sets) to interact with each other.

[0114] Processor 1404 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1404A, central processing unit circuitry (CPU) 1404B, and graphics processing unit circuitry (GPU) 1404C. Processor 1404 may include any type of circuit or processor circuitry that executes or otherwise operates on computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage 1412) to cause UE 1400 to perform the operations described herein.

[0115] In some embodiments, baseband processor circuitry 1404A may access communication protocol stack 1436 in memory / storage 1412 to communicate via a 3GPP-compatible network. Generally speaking, baseband processor circuitry 1404A may access communication protocol stack 1436 to perform the following operations: execute user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and execute control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of RF interface circuitry 1408.

[0116] Baseband processor circuitry 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveform for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0117] The memory / storage device 1412 may include one or more non-transitory computer-readable media that include instructions (e.g., communication protocol stack 1436) that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform the various operations described herein. The memory / storage device 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage device 1412 may be located on the processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage device 1412 is located external to the processor 1404 but may be accessed via a memory interface. The memory / storage device 1412 may comprise any suitable volatile or non-volatile memory, such as but not limited to 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. In some embodiments, the memory / storage device 1412 may include a subscriber identity module (SIM) / universal subscriber identity module (USIM).

[0118] In some embodiments, the UE 1400 may include a universal integrated circuit card (UICC) removably coupled to the platform circuitry of the UE 1400 via, for example, a card slot. The UICC may include portions of the processor 1404 and the memory / storage device 1412 and may include the SIM / USIM. In other embodiments, the components of the UICC may be directly integrated into the platform circuitry of the UE 1400 (e.g., permanently coupled to the platform circuitry).

[0119] The RF interface circuit 1408 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1400 to communicate with other devices via a radio access network. The RF interface circuit 1408 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0120] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 1426 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the receiver of the transceiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1404.

[0121] In the transmit 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 signal through a power amplifier before the RF signal is radiated across the air interface via the antenna structure 1426.

[0122] In various embodiments, the RF interface circuit 1408 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0123] The antenna structure 1426 may include antenna elements to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. These antenna elements may be arranged into one or more antenna panels. The antenna structure 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input / multiple-output communication. The antenna structure 1426 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, or a phased array antenna. The antenna structure 1426 may have one or more panels designed for a specific frequency band, including bands in FR1 or FR2.

[0124] The user interface 1416 includes various input / output (I / O) devices that are designed to enable a user to interact with the UE 1400. The user interface 1416 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual component for accepting input, particularly 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, or a headset, etc. The output device circuitry includes any physical or virtual component for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number or combination of audio or visual displays, particularly including 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 a display device or a touchscreen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, and a projector), where the output of characters, graphics, multimedia objects, etc. is generated or produced through the operation of the UE 1400.

[0125] Sensor 1420 may include a device, module, or subsystem aimed at detecting events or changes in its environment and sending information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including three-axis accelerometers, three-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0126] Driver circuit 1422 may include software elements and hardware elements operating to control specific devices embedded in, attached to, or otherwise communicatively coupled to UE 1400. Driver circuit 1422 may include various drivers, thereby allowing other components to interact with or control various I / O devices that may be present within or connected to UE 1400. For example, driver circuit 1422 may include circuitry facilitating the coupling of a UICC (e.g., UICC 148) to UE 1400. In additional examples, driver circuit 1422 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 obtaining sensor readings from sensor 1420 and controlling and allowing access to sensor 1420; a driver for obtaining the actuator position of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; an audio driver for controlling and allowing access to one or more audio devices.

[0127] PMIC 1424 may manage the power provided to various components of UE 1400. Specifically, for processor 1404, PMIC 1424 may control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0128] In some embodiments, PMIC 1424 may control or otherwise be part of various power-saving mechanisms of UE 1400, which include DRX, as discussed herein.

[0129] The battery 1428 can power the UE 1400, but in some examples, the UE 1400 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1428 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1428 can be a typical lead-acid car battery.

[0130] Figure 15 A network node 1500 according to some embodiments is shown. Network node 1500 may be similar to and substantially interchangeable with base station 108, a device implementing one of network hops 154, an IAB node, a network controlled repeater, or a server in a core network or external data network.

[0131] The network node 1500 may include a processor 1504 , RF interface circuitry 1508 (if implemented as an access node), core network (CN) interface circuitry 1512 , memory / storage circuitry 1516 , and antenna structures 1526 .

[0132] Components of network node 1500 may be coupled to various other components via one or more interconnects 1528 .

[0133] The processor 1504, RF interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna structure 1526 and interconnect 1528 may be similar to those of reference Figure 14 Like named elements are shown and described.

[0134] The CN interface circuit 1512 may provide a connection to a core network (e.g., a 5GC using a 5th generation core network (5GC) compatible network interface protocol such as a carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the network node 1500 via optical fiber or wireless backhaul. The CN interface circuit 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1512 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0135] In some embodiments, the network node 1500 may use antenna structures 1526, CN interface circuits, or other interface circuits to couple to a transmit receive point (TRP).

[0136] As is well known, the use of personally identifiable information should comply with privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of the authorized use should be clearly explained to users.

[0137] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, or methods described in the following embodiment section. For example, the baseband circuit described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the following examples. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the examples set forth in the following example section.

[0138] Embodiment

[0139] In the following sections, additional exemplary aspects are provided.

[0140] Embodiment 1 includes a method that includes: receiving information associating eight TCI code points with respective combinations of four TCI states; receiving downlink control information (DCI) having a three-bit value in a transmit configuration indicator (TCI) code point field to indicate a first TCI code point among the eight TCI code points, where the first TCI code point is configured with a first combination of four TCI states; and processing an uplink transmission or a downlink transmission based on one or more of the TCI states in the first combination of four TCI states.

[0141] Embodiment 2 includes the method according to Embodiment 1 or some other embodiment herein, where the first combination of four TCI states includes a first TCI state, a second TCI state, a third TCI state, and a fourth TCI state, the DCI further includes a four-bit value in an application field, and the method further includes: determining whether to update a first downlink TCI state to the first TCI state based on a first bit of the four-bit value; determining whether to update a first uplink TCI state to the second TCI state based on a second bit of the four-bit value; determining whether to update a second downlink TCI state to the third TCI state based on a third bit of the four-bit value; and determining whether to update a second uplink TCI state to the fourth TCI state based on a fourth bit of the four-bit value.

[0142] Embodiment 3 includes the method according to Embodiment 1 or some other embodiment herein, wherein the DCI further includes a two-bit value in the application field, and the method further includes: determining, based on the first bit of the two-bit value, whether to update a first downlink TCI state to a first TCI state among the four TCI states and whether to update a second downlink TCI state to a second TCI state among the four TCI states; and determining, based on the second bit of the two-bit value, whether to update a first uplink TCI state to a third TCI state among the four TCI states and whether to update a second uplink TCI state to a fourth TCI state among the four TCI states.

[0143] Embodiment 4 includes the method according to Embodiment 1 or some other embodiment herein, wherein the DCI further includes a two-bit value in the application field, and the method further includes: determining, based on the first bit of the two-bit value, whether to update a first downlink TCI state to a first TCI state among the four TCI states and whether to update a first uplink TCI state to a second TCI state among the four TCI states; and determining, based on the second bit of the two-bit value, whether to update a second downlink TCI state to a third TCI state among the four TCI states and whether to update a second uplink TCI state to a fourth TCI state among the four TCI states.

[0144] Embodiment 5 includes a method, the method including: receiving a first media access control (MAC) control element (CE) having a first list identifier (ID) and a first plurality of transmit configuration indicator (TCI) state identifiers; and receiving a second MAC CE having a second list ID and a second plurality of TCI state identifiers; configuring a first TCI state list based on the first MAC CE; and configuring a second TCI state list based on the second MAC CE.

[0145] Embodiment 6 includes the method according to Embodiment 5 or some other embodiment herein, wherein the method further includes: receiving downlink control information (DCI) having a first three-bit value in a first TCI code point field and a second three-bit value in a second TCI code point field; and identifying a first one or more TCI states from the first TCI state list based on the first three-bit value; and identifying a second one or more TCI states from the second TCI state list based on the second three-bit value.

[0146] Embodiment 7 includes the method according to Embodiment 6 or some other embodiment herein, wherein the DCI includes DCI format 1_1 or DCI format 1_2 in the presence or absence of data scheduling.

[0147] Example 8 includes the method according to Example 5 or some other example herein, wherein the method further includes: receiving downlink control information (DCI) having a first value in a setting field and a second value in a TCI code point field, wherein the first value is a one-bit value or a two-bit value, and the second value is a three-bit value; and selecting one or more indicated lists from the first TCI state list and the second TCI state list based on the first value; and identifying at least one TCI state from the one or more indicated lists based on the three-bit value.

[0148] Example 9 includes the method according to Example 8 or some other example herein, wherein the first value is a one-bit value, the selecting includes: selecting one indicated list from the first TCI state list and the second TCI state list based on the first value, and the identifying the at least one TCI state includes: identifying at least one TCI state from the one indicated list.

[0149] Example 10 includes the method according to Example 8 or some other example herein, wherein the first value is a two-bit value, and the selecting the one or more indicated lists includes: determining whether the first TCI state list is included in the one or more indicated lists based on the first bit of the two-bit value; and determining whether the second TCI state list is included in the one or more indicated lists based on the second bit of the two-bit value.

[0150] Example 11 includes the method according to Example 5 or some other example herein, wherein the first list ID is associated with a first transmit receive point (TRP), and the second list ID is associated with a second TRP.

[0151] Example 12 includes a method, the method includes: sending a first medium access control (MAC) control element (CE) having a first list identifier (ID) and a first plurality of transmit configuration indicator (TCI) state identifiers to configure a first TCI state list; and sending a second MAC CE having a second list ID and a second plurality of TCI state identifiers to configure a second TCI state list.

[0152] Example 13 includes the method according to Example 12 or some other example herein, wherein the method further includes: transmitting downlink control information (DCI) having a first three-bit value in a first TCI code point field and a second three-bit value in a second TCI code point field, wherein the first three-bit value is used to identify a first one or more TCI states from the first TCI state, and the second three-bit value is used to identify a second one or more TCI states from the second TCI state list.

[0153] Example 14 includes the method according to Example 13 or some other example herein, wherein the DCI includes DCI format 1_1 or DCI format 1_2 in the presence or absence of data scheduling.

[0154] Example 15 includes a method, the method including: identifying two unified downlink TCI states associated with a transmission configuration indicator (TCI) code point; determining that one or both of the two unified downlink TCI states will be used as a default TCI state; and receiving a physical downlink shared channel (PDSCH) transmission based on the default TCI state.

[0155] Example 16 includes the method according to Example 15 or some other example herein, the method further including: receiving radio resource control (RRC) parameters in a control resource set (CORESET) configuration or a PDSCH configuration; and determining that one or both of the two unified downlink TCI states will be used as a default TCI state based on the RRC parameters.

[0156] Example 17 includes the method according to Example 16 or some other example herein, the method further including: receiving downlink control information (DCI) for scheduling the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state configured by the RRC parameters.

[0157] Example 18 includes the method according to Example 15 or some other example herein, the method further including: receiving downlink control information (DCI) for scheduling the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state based on determining that the time between receiving the DCI and receiving the PDSCH transmission is less than a predetermined threshold.

[0158] Example 19 includes the method according to Example 18 or some other example herein, the method further including: transmitting an indication of the predetermined threshold in a UE capability report.

[0159] Embodiment 20 includes the method according to Embodiment 19 or some other embodiment herein, wherein the predetermined threshold is associated with a subcarrier spacing (SCS).

[0160] Embodiment 21 includes the method according to Embodiment 15 or some other embodiment herein, the method further comprising: determining a quasi - co - location (QCL) assumption for a lowest control resource set (CORESET) identifier (ID); and determining, based on the QCL assumption of the lowest CORESET identifier, that one or both of the two unified downlink TCI states will be used as a default TCI state.

[0161] Embodiment 22 includes the method according to Embodiment 15 or some other embodiment herein, the method further comprising: receiving an instruction in a radio resource control (RRC) signal; and determining, based on the instruction, whether a first mode or a second mode will be used when determining the default TCI state, wherein the first mode is based on RRC parameters in a control resource set (CORESET) configuration or a PDSCH configuration, and the second mode is based on one or more TCI states for monitoring a control resource set (CORESET).

[0162] Embodiment 23 includes the method according to Embodiment 15 or some other embodiment herein, wherein the PDSCH transmission is a first PDSCH transmission, and the method further comprising: receiving downlink control information (DCI) for scheduling a second PDSCH transmission, the DCI including a TCI code point field to indicate one or both of the two unified downlink TCI states; and determining, based on the TCI code point field, that one or both of the two unified downlink TCI states will be used as a default TCI state, wherein the first PDSCH transmission will occur after the second PDSCH transmission.

[0163] Embodiment 24 includes the method according to Embodiment 23 or some other embodiment herein, the method further comprising: receiving the first PDSCH transmission after a time period greater than the quasi - co - location (QCL) duration since receiving the DCI.

[0164] Another embodiment may include one or more non - transitory computer - readable media, the one or more non - transitory computer - readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method according to any one of Embodiments 1 to 23 or related thereto or any other method or process described herein.

[0165] Another embodiment may include an apparatus that includes logic components, modules, or circuitry for performing one or more elements of a method according to any one of embodiments 1 to 23 or related thereto or any other method or process described herein.

[0166] Another embodiment may include a method, technique, or process according to any one of embodiments 1 to 23 or a part or component thereof or related thereto.

[0167] Another embodiment may include an apparatus that includes: one or more processors, and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process according to any one of embodiments 1 to 23 or a part or related thereto.

[0168] Another embodiment includes a signal according to any one of embodiments 1 to 23 or a part or component thereof or related thereto.

[0169] Another embodiment may include a datagram, information element, packet, frame, segment, PDU, or message according to any one of embodiments 1 to 23 or a part or component thereof or related thereto or otherwise described in the present disclosure.

[0170] Another embodiment may include a signal encoded with data according to any one of embodiments 1 to 23 or a part or component thereof or related thereto or otherwise described in the present disclosure.

[0171] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message according to any one of embodiments 1 to 23 or a part or component thereof or related thereto or otherwise described in the present disclosure.

[0172] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process according to any one of embodiments 1 to 23 or a part or related thereto.

[0173] Another embodiment may include a computer program that includes instructions, where execution of the program by a processing element will cause the processing element to perform a method, technique, or process according to any one of embodiments 1 to 23 or a part or related thereto.

[0174] Another embodiment may include a signal in a wireless network as shown and described herein.

[0175] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0176] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0177] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0178] Unless otherwise expressly stated, any one of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practice of the various aspects.

[0179] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be interpreted to cover all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause a user equipment (UE) to: Receive information associating eight TCI code points with respective combinations of four TCI states; Receive downlink control information (DCI) having a three-bit value in a transmission configuration indicator (TCI) code point field to indicate a first TCI code point among the eight TCI code points, wherein the first TCI code point is configured with a first combination of four TCI states; and Process an uplink transmission or a downlink transmission based on one or more TCI states in the first combination of four TCI states.

2. The one or more computer-readable media according to claim 1, wherein the first combination of four TCI states includes a first TCI state, a second TCI state, a third TCI state, and a fourth TCI state, the DCI further includes a four-bit value in an application field, and the instructions, when executed, further cause the UE to: Determine whether to update a first downlink TCI state to the first TCI state based on a first bit of the four-bit value; Determine whether to update a first uplink TCI state to the second TCI state based on a second bit of the four-bit value; Determine whether to update a second downlink TCI state to the third TCI state based on a third bit of the four-bit value; and And Determine whether to update a second uplink TCI state to the fourth TCI state based on a fourth bit of the four-bit value.

3. The one or more computer-readable media according to claim 1, wherein the DCI further includes a two-bit value in an application field, and the instructions, when executed, further cause the UE to: Determine whether to update a first downlink TCI state to the first TCI state among the four TCI states and whether to update a second downlink TCI state to the second TCI state among the four TCI states based on a first bit of the two-bit value; and Determine whether to update a first uplink TCI state to the third TCI state among the four TCI states and whether to update a second uplink TCI state to the fourth TCI state among the four TCI states based on a second bit of the two-bit value.

4. The one or more computer-readable media according to claim 1, wherein the DCI further includes a two-bit value in an application field, and the instructions, when executed, cause the UE to: Determine whether to update a first downlink TCI state to the first TCI state among the four TCI states and whether to update a first uplink TCI state to the second TCI state among the four TCI states based on a first bit of the two-bit value; and Determine whether to update a second downlink TCI state to the third TCI state among the four TCI states and whether to update a second uplink TCI state to the fourth TCI state among the four TCI states based on a second bit of the two-bit value.

5. An apparatus, the apparatus comprising circuitry for: receiving a first Medium Access Control (MAC) Control Element (CE) having a first List Identifier (ID) and a first plurality of Transmission Configuration Indicator (TCI) status identifiers ； and receiving a second MAC CE having a second List ID and a second plurality of TCI status identifiers; configuring a first TCI status list based on the first MAC CE; and configuring a second TCI status list based on the second MAC CE.

6. The apparatus according to claim 5, wherein the circuitry is further for: receiving Downlink Control Information (DCI) having a first three-bit value in a first TCI code point field and a second three-bit value in a second TCI code point field ； and identifying first one or more TCI statuses from the first TCI status list based on the first three-bit value; and identifying second one or more TCI statuses from the second TCI status list based on the second three-bit value.

7. The apparatus according to claim 6, wherein the DCI comprises DCI format 1_1 or DCI format 1_2 in the presence or absence of data scheduling.

8. The apparatus according to claim 5, wherein the circuitry is further for: receiving Downlink Control Information (DCI) having a first value in a set field and a second value in a TCI code point field, wherein the first value is a one-bit value or a two-bit value, and the second value is a three-bit value; and selecting one or more indicated lists from the first TCI status list and the second TCI status list based on the first value; and identifying at least one TCI status from the one or more indicated lists based on the three-bit value.

9. The apparatus according to claim 8, wherein the first value is a one-bit value, the selection comprises: selecting one indicated list from the first TCI status list and the second TCI status list based on the first value, and the identifying the at least one TCI status comprises: identifying at least one TCI status from the one indicated list.

10. The apparatus according to claim 8, wherein the first value is a two-bit value, and for selecting the one or more indicated lists, the circuitry is for: determining whether the first TCI status list is included in the one or more indicated lists based on a first bit of the two-bit value; and determining whether the second TCI status list is included in the one or more indicated lists based on a second bit of the two-bit value.

11. The apparatus according to claim 5, wherein the first List ID is associated with a first Transmission and Reception Point (TRP), and the second List ID is associated with a second TRP.

12. A method, the method comprises: transmitting a first Medium Access Control (MAC) Control Element (CE) having a first List Identifier (ID) and a first plurality of Transmission Configuration Indicator (TCI) status identifiers to configure a first TCI status list; and Transmit a second MAC CE with a second list ID and a second plurality of TCI state identifiers to configure a second TCI state list.

13. The method according to claim 12, wherein the method further comprises: transmitting downlink control information (DCI) having a first three-bit value in a first TCI code point field and a second three-bit value in a second TCI code point field, wherein the first three-bit value is used to identify a first one or more TCI states from the first TCI state, and the second three-bit value is used to identify a second one or more TCI states from the second TCI state list.

14. The method according to claim 13, wherein the DCI comprises DCI format 1_1 or DCI format 1_2 in the presence or absence of data scheduling.

15. A method, the method comprises: identifying two unified downlink TCI states associated with a transmit configuration indicator (TCI) code point; determining that one or both of the two unified downlink TCI states will be used as a default TCI state; and receiving a physical downlink shared channel (PDSCH) transmission based on the default TCI state.

16. The method according to claim 15, the method further comprises: receiving radio resource control (RRC) parameters in a control resource set (CORESET) configuration or a PDSCH configuration; and determining that one or both of the two unified downlink TCI states will be used as a default TCI state based on the RRC parameters.

17. The method according to claim 16, the method further comprises: receiving downlink control information (DCI) for scheduling the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state configured by the RRC parameters.

18. The method according to claim 15, the method further comprises: receiving downlink control information (DCI) for scheduling the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state based on determining that a time between receiving the DCI and receiving the PDSCH transmission is less than a predetermined threshold.

19. The method according to claim 18, the method further comprises: sending an indication of the predetermined threshold in a UE capability report.

20. The method according to claim 19, wherein the predetermined threshold is associated with a subcarrier spacing (SCS).

21. The method according to claim 15, the method further comprises: determining a quasi-co-location (QCL) assumption for a lowest control resource set (CORESET) identifier (ID); and determining that one or both of the two unified downlink TCI states will be used as a default TCI state based on the QCL assumption of the lowest CORESET identifier.

22. The method according to claim 15, the method further comprises: Receive an instruction in a Radio Resource Control (RRC) signal; and determine, based on the instruction, whether a first mode or a second mode will be used when determining the default TCI state, wherein the first mode is based on RRC parameters in a Control Resource Set (CORESET) configuration or a PDSCH configuration, and the second mode is based on one or more TCI states for monitoring a Control Resource Set (CORESET).

23. The method according to claim 15, wherein the PDSCH transmission is a first PDSCH transmission, and the method further comprises: receiving downlink control information (DCI) for scheduling a second PDSCH transmission, the DCI including a TCI code point field to indicate one or both of the two unified downlink TCI states; and determining, based on the TCI code point field, that one or both of the two unified downlink TCI states will be used as the default TCI state, wherein the first PDSCH transmission will occur after the second PDSCH transmission.

24. The method according to claim 23, the method further comprises: receiving the first PDSCH transmission after a time period greater than a quasi-co-location (QCL) duration since receiving the DCI.

Images