WO2024092623A1 - Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant - Google Patents

Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant Download PDF

Info

Publication number
WO2024092623A1
WO2024092623A1 PCT/CN2022/129574 CN2022129574W WO2024092623A1 WO 2024092623 A1 WO2024092623 A1 WO 2024092623A1 CN 2022129574 W CN2022129574 W CN 2022129574W WO 2024092623 A1 WO2024092623 A1 WO 2024092623A1
Authority
WO
WIPO (PCT)
Prior art keywords
tci
state
dci
list
states
Prior art date
Application number
PCT/CN2022/129574
Other languages
English (en)
Inventor
Hong He
Chunhai Yao
Sigen Ye
Weidong Yang
Dawei Zhang
Wei Zeng
Jie Cui
Chunxuan Ye
Huaning Niu
Original Assignee
Apple Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc. filed Critical Apple Inc.
Priority to PCT/CN2022/129574 priority Critical patent/WO2024092623A1/fr
Publication of WO2024092623A1 publication Critical patent/WO2024092623A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • This application relates generally to communication networks and, in particular, to technologies for technologies for transmission configuration indicator association for physical downlink shared channel reception.
  • a user equipment may be connected with a network through multiple transmit/receive points (TRPs) .
  • TRPs transmit/receive points
  • mTRP multi-TRP
  • different TRPs may provide different data for spatial multiplexing or the same data to improve robustness.
  • Multi-TRP may be supported by a single-downlink control information (DCI) mode and multi-DCI mode.
  • DCI single-downlink control information
  • sDCI single-DCI
  • sDCI single-DCI
  • sDCI single-DCI
  • TRPs may independently schedule their own PDSCH.
  • FIG. 1 illustrates a network environment in accordance with some embodiments.
  • FIG. 2 illustrates a codepoint setting in accordance with some embodiments.
  • FIG. 3 illustrates media access control (MAC) control element (CE) in accordance with some embodiments.
  • MAC media access control
  • CE control element
  • FIG. 4 illustrates a pair of transmission configuration indicator (TCI) -state lists and DCI in accordance with some embodiments.
  • TCI transmission configuration indicator
  • FIG. 5 illustrates another pair of TCI-state lists and DCI in accordance with some embodiments.
  • FIG. 6 illustrates another pair of TCI-state lists and DCI in accordance with some embodiments.
  • FIG. 7 illustrates DCI in accordance with some embodiments.
  • FIG. 8 illustrates an example operation for updating TCI states in accordance with some embodiments.
  • FIG. 9 illustrates another example operation for updating TCI states in accordance with some embodiments.
  • FIG. 10 illustrates a signaling diagram in accordance with some embodiments.
  • FIG. 11 illustrates an operational flow/algorithmic structure in accordance with some embodiments.
  • FIG. 12 another operational flow/algorithmic structure in accordance with some embodiments.
  • FIG. 13 illustrates another operational flow/algorithmic structure in accordance with some embodiments.
  • FIG. 14 illustrates an user equipment in accordance with some embodiments.
  • FIG. 15 illustrates a network node in accordance with some embodiments.
  • the phrase “A or B” means (A) , (B) , or (A and B) ; and the phrase “based on A” means “based at least in part on A, ” for example, it could be “based solely on A” or it could be “based in part on A. ”
  • circuitry refers to, is part of, or includes hardware components, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an application specific integrated circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , and/or digital signal processors (DSPs) , that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • SoC programmable system-on-a-chip
  • DSPs digital signal processors
  • circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • circuitry may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these aspects, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations; or recording, storing, or transferring digital data.
  • processor circuitry may refer an application processor; 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 capable of executing or otherwise operating computer-executable instructions, such as program code; software modules; or functional processes.
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces; for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, 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.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • computer system refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
  • 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 computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, or the like.
  • a “hardware resource” may refer to computer, storage, or network resources provided by physical hardware element (s) .
  • a “virtualized resource” may refer to computer, storage, or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services and may include computing or network resources. System resources may be considered 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 are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices for the purpose of transmitting and receiving information.
  • instantiate, ” “instantiation, ” and the like as used herein refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • connection may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
  • network element refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element or a data element that contains content.
  • An information element may include one or more additional information elements.
  • multi- refers to more than one.
  • FIG. 1 illustrates a network environment 100 in accordance with some embodiments.
  • the network environment 100 may include a UE 104 and a base station (BS) 108.
  • the base station 108 may provide one or more wireless access cells, for example, Third Generation Partnership Project (3GPP) New Radio (NR) cells, through which the UE 104 may communicate with the base station 108.
  • 3GPP Third Generation Partnership Project
  • NR New Radio
  • the UE 104 and the base station 108 may communicate over an air interface compatible with 3GPP technical specifications such as those that define Fifth Generation (5G) NR or later generation system standards.
  • 5G Fifth Generation
  • the base station 108 may include a controller 112 coupled with one or more TRPs, for example, TRP 116 and TRP 120.
  • the controller 112 may perform the majority of the operations of a communication protocol stack, including scheduling, while the TRPs 116 and 120 act as distributed antennas.
  • the TRPs 116 and 120 may perform some lower-level operations of the communication protocol stack (for example, analog physical (PHY) layer operations) . While FIG. 1 shows the TRPs 116 and 120 as part of the base station 108, in other embodiments, the TRPs 116 and 120 may be associated with different base stations.
  • PHY physical
  • the base station 108 may use the TRPs 116 and 122 to geographically separate points at which a signal may be transmitted to, or received from, the UE 104. This may increase flexibility of using multiple-input, multiple-output (MIMO) and beamforming enhancements for communicating with the UE 104.
  • the TRPs 116 and 120 may be used to transmit the same or different downlink transmissions to the UE 104.
  • the distributed transmit/receive capabilities provided by the TRPs 116 and 120 may be used for coordinated multipoint or carrier aggregation systems.
  • DCI transmitted by a single TRP may schedule physical downlink shared channel (PDSCH) transmissions from a plurality of TRPs, for example TRP 116 and TRP 120.
  • the DCI may schedule a PDSCH transmission by indicating a PDSCH transmission occasion in which the PDSCH may be transmitted.
  • TRP 116 is to transmit a first PDSCH transmission (PDSCH 1)
  • TRP 120 is to transmit a second PDSCH transmission (PDSCH 2) in respective PDSCH transmission occasions.
  • PDSCH 1 and PDSCH 2 may include the same or different information.
  • Radio channels may experience different radio channels.
  • different antenna ports may share common radio channel characteristics.
  • different antenna ports may have similar Doppler shifts, Doppler spreads, average delay, delay spread, or spatial receive parameters (for example, properties associated with a downlink received signal angle of arrival at a UE) .
  • Antenna ports that share one or more of these large-scale radio channel characteristics may be said to be quasi co-located with one another.
  • 3GPP has specified four types of quasi co-location (QCL) to indicate which particular channel characteristics are shared.
  • QCL Type A antenna ports share Doppler shift, Doppler spread, average delay, and delay spread.
  • QCL Type B antenna ports share Doppler shift and Doppler spread are shared.
  • QCL Type C antenna ports share Doppler shift and average delay.
  • antenna ports share spatial receiver parameters.
  • the base station 108 may provide transmission configuration indicator (TCI) state information to the UE 104 to indicate QCL relationships between antenna ports used for reference signals (for example, synchronization signal/physical broadcast channel (PBCH) or channel state information-reference signal (CSI-RS) ) and downlink data or control signaling, for example, PDSCH or physical downlink control channel (PDCCH) .
  • TCI transmission configuration indicator
  • the base station 108 may use a combination of radio resource control (RRC) signaling, MAC CE signaling, and DCI, to inform the UE 104 of these QCL relationships.
  • RRC radio resource control
  • the base station 108 may configure the UE 104 with a plurality of TCI states through RRC signaling.
  • up to 128 TCI states may be configured for PDSCH through, for example, a PDSCH-config information element
  • up to 64 TCI states may be configured for PDCCH through, for example, a PDCCH-config information element.
  • Each TCI state may include a cell identifier, a bandwidth part identifier, an indication of the relevant SS/PBCH block or CSI-RS, and an indication of the QCL type.
  • the TCI states may be set as inactive after initial configuration.
  • the base station 108 may then transmit an activation command through, for example, a MAC CE.
  • the activation command may activate up to eight combinations of TCI states that correspond to eight codepoints of a TCI codepoint field in DCI.
  • One or more specific TCI states may then be dynamically selected and signaled using the TCI codepoint field in DCI to indicate which of the active TCI states are applicable to a PDSCH resource allocation.
  • the initial state framework of 3GPP Release 15 provided that TCI states were separately indicated for different DL channels (e.g., PDSCH and PDCCH) , which may result in the different DL channels using different active TCI states. While this provided significant flexibility, it was also associated with a large signaling overhead.
  • Release 17 of 3GPP developed a unified TCI framework to facilitate streamlined multi-beam operation targeting higher frequency ranges, for example, frequency range 2 (FR2) from 24, 250 megahertz (MHz) to 71,000 MHz.
  • FR2 frequency range 2
  • a single active TCI state may be used as a unified downlink TCI state to be applied for all PDSCH/PDCCH channels.
  • a unified uplink TCI state may also be defined/applied for uplink channels (e.g., physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) .
  • uplink channels e.g., physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) .
  • the Release 17 unified TCI framework focuses on sTRP use cases. Extension of the unified TCI framework to mTRP use cases may be beneficial.
  • up to four TCI states may be indicated in a component carrier (CC) /bandwidth part (BWP) or a set of CCs/BWPs in a CC list.
  • the up to four TCI states which may be used for DL receptions or UL transmissions, may be indicated/updated by a MAC CE or DCI with MAC CE based TCI state activation.
  • Embodiments of the present disclosure address various issues in order to ensure flexibility of unified TCI states indication for mTRP.
  • the TCI codepoint field in DCI may include three-bits, which supports eight combinations of TCI states with each combination being associated with a codepoint of the TCI codepoint field.
  • Each combination can include up to four TCI states, e.g., TCI state #1, TCI state #2, TCI state #3, and TCI state #4.
  • TCI state #1 TCI state #1
  • TCI state #2 TCI state #2
  • TCI state #3 TCI state #4.
  • support for up to 8*8*8*8 4096 combinations would be required for support of up to eight candidates with full flexibility. This would require a 12-bit indication.
  • Embodiments describe how to use the 3-bit TCI codepoint field to efficiently update 4, 096 TCI state combinations for mTRPs (for example, two TRPs) .
  • embodiments describe how to associate two indicated downlink TCI states by TCI codepoint with a PDSCH reception in sDCI mTRP.
  • each TCI codepoint in DCI may always be associated with four TCI states.
  • FIG. 2 illustrates an example codepoint setting 200 in accordance with the first aspect.
  • the codepoint setting 200 may include eight codepoints, which may be indicated through a 3-bit TCI codepoint field in DCI. Each of the eight codepoints may be associated with different combinations of four TCI states.
  • the four TCI states of the codepoints may correspond to two uplink TCI states and two downlink TCI states.
  • the four TCI states may respectively correspond to a DL state #1 (e.g., TCI state the UE 104 is to use to receive downlink transmissions from TRP #1) , an UL state #1 (e.g., TCI state the UE 104 is to use to transmit uplink transmissions to TRP #1) , DL state #2 (e.g., TCI state the UE 104 is to use to receive downlink transmissions from TRP #2) , and an UL state #2 (e.g., TCI state the UE 104 is to use to transmit uplink transmissions to TRP #2) .
  • DL state #1 e.g., TCI state the UE 104 is to use to transmit uplink transmissions to TRP #1
  • DL state #2 e.g., TCI state the UE 104 is to use to receive downlink transmissions from TRP #2
  • an UL state #2 e.g., TCI state the UE 104 is to use to transmit uplink transmissions to TRP #2
  • a second aspect for providing a unified TCI state indication for sDCI mTRP may rely on TRP-specific activated TCI-state lists.
  • MAC CEs may be used for TRP-specific TCI state activation followed by unified TCI states indication for multiple TRPs.
  • FIG. 3 illustrates a MAC CE 300 that may be used to activate/deactivate TCI states of a TCI-state list that is specific to a TRP in accordance with some embodiments.
  • 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 applies to a first TCI-state list or a second TCI-state list.
  • ID list identifier
  • the list ID may be referred to with other names such as virtual ID, set ID, TRP ID, etc.
  • the first octet may further include a 5-bit field for a serving cell ID and a 2-bit field for DL BWP ID to respectively indicate identities of the serving cell and DL BWP to which the MAC CE applies.
  • the MAC CE 300 may include a number of reserved fields, marked as “R, ” and may include a 2-bit field for UL BWP ID to indicate an identity of an UL BWP to which the MAC CE applies.
  • the P i fields of the third octet may be used to indicate whether each TCI codepoint has multiple TCI states or a single TCI state. For example, if the P 2 field is set to 1, the second TCI codepoint includes multiple TCI states.
  • Octet 4 through octet N+3 respectively configure TCI state IDs 1 –N.
  • the D/U field may be used to indicate whether the TCI state ID in the same octet is for joint/downlink or uplink TCI state. If the field is set to 1, the TCI state ID is for joint/downlink.
  • Each element in a list may include a TCI state for a joint/downlink state, an UL state, or both.
  • FIG. 4 illustrates a pair of TCI-state lists 400 and DCI 404 that may be used in unified TCI-state indication for multiple TRPs in accordance with some embodiments.
  • the pair of TCI-state lists 400 may include a first TCI-state list 408 and a second TCI-state list 412.
  • first TCI-state list 408 may correspond to a first TRP (e.g., TRP 116) while the second TCI-state list corresponds to a second T
  • the DCI 404 may include two 3-bit TCI codepoint fields, a number of other fields, and a cyclic redundancy check (CRC) field.
  • the first 3-bit TCI codepoint field may be set with a value of ‘101’ to indicate that the TCI state set of the fifth TCI codepoint is to be used as the unified TCI state (s) for the first TRP.
  • the second 3-bit TCI codepoint field may be set with a value of ‘001’ to indicate that the TCI state set of the second TCI codepoint is to be used as the unified TCI state (s) for the second TRP.
  • use of two 3-bit TCI codepoint fields may be limited to DCI format 1_1/1_2 without data scheduling. This may be done by repurposing the previously-reserved fields of DCI format 1_1/1_2 as the second TCI codepoint field.
  • FIG. 5 illustrates a pair of TCI-state lists 500 and DCI 504 that may be used in unified TCI-state indication for multiple TRPs in accordance with some embodiments.
  • the pair of TCI-state lists 500 may include a first TCI-state list 508 and a second TCI-state list 512.
  • the first TCI-state list 508 and the second TCI-state list 512 may be activated in a manner similar to that discussed above with respect to FIGs. 3 and 4.
  • the DCI 504 may include a 1-bit list ID field, a 3-bit TCI codepoint field, a number of other fields, and a CRC field.
  • the 1-bit list ID field may be used to indicate whether the TCI state (s) indicated by the TCI codepoint field applies 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 codepoint field is set to ‘101, ’ the UE 104 may determine that the fifth TCI codepoint is to be used as the unified TCI state (s) for the first TRP only.
  • the UE 104 may determine that the fifth TCI codepoint is to be used as the unified TCI state (s) for the second TRP only.
  • FIG. 6 illustrates a pair of TCI-state lists 600 and DCI 604 that may be used in unified TCI-state indication for multiple TRPs in accordance with some embodiments.
  • the pair of TCI-state lists 600 may include a first TCI-state list 608 and a second TCI-state list 612.
  • the first TCI-state list 608 and the second TCI-state list 612 may be activated in a manner similar to that discussed above with respect to FIGs. 3 and 4.
  • the DCI 604 may include a 2-bit list ID field, a 3-bit TCI codepoint field, a number of other fields, and a CRC field.
  • the 2-bit list ID field may be used to indicate whether the TCI state (s) indicated by the TCI codepoint field applies to the first TCI-state list 508 or the second TCI-state list 512.
  • a first bit (b 0 ) of the 2-bit list ID field may be set to indicate whether the TCI state (s) indicated by the TCI codepoint field applies to the first TRP and a second bit (b 0 ) of the 2-bit list ID field may be set to indicate whether the TCI state (s) indicated by the TCI codepoint field applies to the second TRP.
  • the UE 104 may determine that the TCI 0, 5 applies to the first TRP and TCI 1, 5 applies to the second TRP.
  • FIG. 7 illustrates a DCI 700 utilizing a bitmap-based TCI-state application indication in accordance with some embodiments.
  • the DCI 700 may have DCI format 1_1/1_2 with or without scheduling.
  • the four TCI states may respectively correspond to a DL state #1, an UL state #1, a DL state #2, and an UL state #2.
  • the DCI 700 may include an application field, a TCI codepoint field, one or more other fields, and a CRC field.
  • the application field may include a bitmap to provide an indication of whether TCI state (s) indicated by the TCI codepoint field apply to the various DL/UL TCI states 704.
  • FIG. 8 illustrates an example operation 800 for updating TCI states based on a bitmap-based TCI state indication in accordance with some embodiments.
  • the UE 104 may be configured with a DL TCI state #4, an UL TCI-state #2, a DL TCI-state #6, and an UL TCI-state #3.
  • the UE 104 may receive DCI (e.g., DCI 700) with an application field set to ‘1101’ and a TCI codepoint value that indicates a TCI codepoint with TCI states #8, #4, #2, and #0. Based on the values of the application field, the UE 104 may determine that the first, second, and fourth TCI states are to be updated based on the TCI states indicated by the TCI codepoint. For example, the 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 corresponding indicated TCI states.
  • DCI e.g., DCI 700
  • the second DL TCI state may not be updated, due to the b 2 bit being set to ‘0, ’ and that TCI state may remain as what it was at T1 (e.g., TCI state #6) .
  • the operation 800 may result in setting a combination of TCI states (e.g., #8, #4, #6, and #0) that may not even be associated with one TCI codepoint.
  • the application field may be used to update TCI states when the TCI codepoint is associated with less than four TCI states. For example, if TCI codepoint is only associated with one TCI state, e.g., TCI state #9, and the bitmap of the application field includes a value of 1101, then the UE 104 may update the DL state #1, UL state #1, and UL state #2 to TCI state #9 and may leave the DL state #2 unchanged.
  • using a bitmap-based TCI state application indication may be applied when TRP-specific activation lists are created by a MAC CE as described with respect to FIGs. 3, 4, 5, and 6.
  • a 2-bit application field may be used in DCI format 1_1/1_2 to provide the bitmap-based TCI-state application indication.
  • a first bit of the application field, b 0 may be used to indicate whether a first set of one or more TCI states are applied or not
  • a second bit of the application field, b 1 may be used to indicate whether a second set of one or more TCI states are applied or not.
  • mapping of the 2-bit application field to the indicated TCI state (s) may be provided by Table 1 or Table 2 below.
  • Tables 1 and 2 map two indicated TCI states to each bit of the application field, in other embodiments other mappings may be used.
  • the first bit may be mapped to the first indicated state while the second bit is mapped to the last three indicated states.
  • FIG. 9 illustrates an example operation 900 for updating TCI states based on a bitmap-based TCI state indication in accordance with some embodiments.
  • the operation 900 may correspond to use of a two-bit application field and a mapping corresponding to Table 1.
  • the UE 104 may be configured with a DL TCI state #4, an UL TCI-state #2, a DL TCI-state #6, and an UL TCI-state #3.
  • the UE 104 may receive DCI with a 2-bit application field set to ‘10’ and a TCI codepoint value that indicates a TCI codepoint with TCI states #8, #4, #2, and #0. Based on the values of the application field, and with reference to Table 1, the UE 104 may determine that the first and third TCI states are to be updated based on the TCI states indicated by the TCI codepoint. For example, the UE 104 may update the first DL TCI state to TCI state #8 and the second DL TCI state to TCI state #2.
  • the UE 104 may determine that the second and fourth TCI states are not to be updated, due to the b 1 bit being set to ‘0, ’ and those TCI states may remain what they were at T1 (e.g., TCI states #2 and #3) .
  • Another aspect of the disclosure may provide for TCI association for PDSCH with sDCI-based mTRP.
  • a variety of signaling approaches may be considered for sDCI-based mTRP to determine applied TCI states, assuming two unified joint/DL TCI states are indicated by a TCI codepoint in DCI format separately.
  • the following four options describe some of the signaling approaches. Some of these options may be used with others. For example, they are not mutually exclusive.
  • an RRC parameter may explicitly indicate which of the two indicated TCI states is to be used for PDSCH reception.
  • the RRC parameter may indicate the first TCI state is to be used for the PDSCH reception, the second TCI state is to be used for the PDSCH reception, or both the first and second TCI states are to be used for the 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 (s) to be used on a per bandwidth part (BWP) basis.
  • a second option may correspond to an instance in which a time offset between a scheduling DCI and a first symbol of the scheduled PDSCH is smaller than a predetermined threshold window.
  • the predetermined threshold window may be referred to as a time duration for QCL (timeDurationForQCL) , which may correspond to an amount of time the UE needs to decode the DCI and, potentially, return RF circuitry based on the TCI state (s) indicated by the DCI before receiving a PDSCH based on the updated TCI state (s) .
  • the UE 104 may provide the base station 108 an indication of the value of timeDurationForQCL as part of a UE capability report. This may be provided on a per subcarrier spacing (SCS) basis.
  • SCS subcarrier spacing
  • FIG. 10 is a signaling diagram 1000 illustrating the timeDurationForQCL in accordance with some embodiments.
  • the signaling diagram 1000 includes a first DCI (DCI #1) that schedules a first PDSCH transmission (PDSCH #1) and a second DCI (DCI #2) that schedules a second PDSCH transmission (PDSCH #2) .
  • the timeDurationForQCL window may start after the last symbol of the PDCCH used to transmit the DCI.
  • the UE 104 may determine default TCI state (s) that it may use to receive PDSCH #1 based on a fixed rule (for example, the first TCI state or the second TCI state is always used as the default TCI state) or based on the first option (for example, according to the RRC parameter of a CORESET/PDSCH configuration) .
  • a fixed rule for example, the first TCI state or the second TCI state is always used as the default TCI state
  • the first option for example, according to the RRC parameter of a CORESET/PDSCH configuration
  • the default TCI state may be the QCL assumption of the lowest CORESET ID in the latest monitored slot.
  • the lowest CC index may be selected.
  • the last TCI state (s) used to monitor PDCCH before receipt of the PDSCH may also be used as the default TCI state (s) for the PDSCH transmission.
  • the UE 104 may use the TCI states indicated by the TCI codepoint field for the reception of the PDSCH transmission.
  • the base station 108 may provide instructions to the UE 104, through RRC signaling, for example, as to whether the UE 104 is to use the first option or the second option. Additionally/alternatively, one of the options (either the first or the second option) may be defined as a default mode and applied unless the other option is explicitly configured.
  • the UE 104 may assume the TCI state indicated by a TCI codepoint field in scheduling DCI is to be applied to PDSCH transmissions received after timeDurationForQCL duration from an ending symbol of the PDCCH that carries the DCI.
  • TCI codepoint field in DCI #1 indicates TCI state #2.
  • DCI #1 schedules PDSCH #1; however, PDSCH #1 is within the timeDurationForQCL window.
  • the UE 104 is unable to apply TCI state #2 to PDSCH #1.Nevertheless, the UE 104 may still update its receive beam based on TCI state #2.
  • TCI state #2 may be applied for PDSCH transmissions received after the timeDurationForQCL window, for example, PDSCH #2 (in the event PDSCH #2 is received within the timeDurationForQCL window of DCI #2 and the UE 104 is unable to use whatever TCI state is indicated in DCI #2) .
  • the indicated TCI states by the TCI codepoint in DCI format may be applied as default beam to PDSCH transmissions within a timeDurationForQCL duration from an ending symbol of the PDCCH that carries the DCI.
  • FIG. 11 illustrates an operation flow/algorithmic structure 1100 in accordance with some embodiments.
  • the operation flow/algorithmic structure 1100 may be implemented by a UE (for example, UE 104) or 1400 or components therein, for example, processors 1404.
  • the operation flow/algorithmic structure 1100 may include, at 1104, receiving information to associate eight TCI codepoints with respective combinations of four TCI states.
  • the configuration information may be received in a MAC CE transmitted from a base station that activates/deactivates the TCI states associated with a particular TCI codepoint.
  • the four TCI states may 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.
  • the TCI states may be unified states.
  • the first DL TCI state may be used for both PDSCH and PDCCH transmissions from the first TRP
  • the first UL TCI state may be used for both PUSCH and PUCCH transmissions to the first TRP, and so on.
  • the operation flow/algorithmic structure 1100 may further include, at 1108, receiving DCI with a 3-bit value in a TCI codepoint field to indicate a first TCI codepoint.
  • the operation flow/algorithmic structure 1100 may further include, at 1112, processing an uplink or downlink transmission based on one or more TCI states associated with the first TCI codepoint.
  • the UE may adjust its transmit or receive beams based on the one or more TCI states.
  • the DCI may include an application field to provide a further indication of which TCI states are to be used to update a configuration of a UE.
  • the application field may be a 4-bit field that includes a bitmap that provides an indication of whether each of the four TCI states are to be used to update a respective TCI state of the UE.
  • the application field may be a 2-bit field with each of the bits providing an indication of whether one or more associated TCI updates are to be used to update respective TCI states of the UE.
  • the associations of the bits to the respective TCI states may be consistent with the mappings of Table 1 and Table 2.
  • FIG. 12 is an operation flow/algorithmic structure 1200 in accordance with some embodiments.
  • the operation flow/algorithmic structure 1200 may be implemented by base station such as, for example, base station 108 or network node 1500 or components therein, for example, processors 1504.
  • the operation flow/algorithmic structure 1200 may include, at 1204, transmitting a first MAC CE having a first list ID and first TCI state IDs to configure a first TCI-state list.
  • the first list ID may be a one bit value that indicates whether the list corresponds to a first TRP or a second TRP.
  • the operation flow/algorithmic structure 1200 may further include, at 1208, transmitting a second MAC CE having a second list ID and second TCI state IDs to configure a second TCI-state list.
  • the second list ID may be a one bit value that indicates whether the list corresponds to the first TRP or the second TRP, whichever complements the first ID list.
  • the base station may indicate specific TCI states using DCI with a TCI codepoint value that corresponds to one or more of the lists.
  • the DCI may include a plurality of TCI codepoint fields.
  • the DCI may include one TCI codepoint field and additional information to indicate whether the TCI codepoint field corresponds to the first list, the second list, or both the first and second lists.
  • FIG. 13 is an operation flow/algorithmic structure 1300 in accordance with some embodiments.
  • the operation flow/algorithmic structure 1300 may be implemented by a UE, for example, UE 104 or 1400 or components therein, for example, processors 1404.
  • the operation flow/algorithmic structure 1300 may include, at 1304, identifying two unified TCI states associated with a TCI codepoint.
  • the operation flow/algorithmic structure 1300 may further include, at 1308, determining one or both of the two unified TCI states are to be used as default TCI state (s) .
  • determining at 1308 may be based on an RRC parameter in a CORESET/PDSCH configuration that provides an explicit indication of which TCI state (s) are to be used as the default TCI state (s) .
  • the default TCI state (s) may be set to the TCI state (s) that the UE uses to monitor for PDCCH transmissions.
  • the default TCI state (s) for a first PDSCH transmission may be set to TCI state (s) indicated in a DCI used to schedule a second PDSCH transmission that occurred prior to the first PDSCH transmission.
  • the operation flow/algorithmic structure 1300 may further include, at 1312, receiving a PDSCH transmission based on the default TCI state (s) .
  • the default TCI state (s) may be used for PDSCH transmissions when a time offset bet okay ween the scheduling DCI and the scheduled PDSCH transmission is less than timeDurationforQCL.
  • the default TCI state (s) may be used for PDSCH transmissions that are not specifically scheduled by a DCI (for example, semi-persistently scheduled PDSCH transmissions) or are scheduled by a DCI that does not include TCI codepoint value.
  • FIG. 14 illustrates a UE 1400 in accordance with some embodiments.
  • the UE 1400 may be similar to and substantially interchangeable with UE 104 of FIG. 1.
  • the UE 1400 may be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, XR device, glasses, industrial wireless sensor (for example, microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, electric voltage/current meter, or actuator) , video surveillance/monitoring device (for example, camera or video camera) , wearable device (for example, a smart watch) , or Internet-of-things device.
  • industrial wireless sensor for example, microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, electric voltage/current meter, or actuator
  • video surveillance/monitoring device for example, camera or video camera
  • wearable device for example, a smart watch
  • Internet-of-things device for example, a smart watch
  • the UE 1400 may include processors 1404, RF interface circuitry 1408, memory/storage 1412, user interface 1416, sensors 1420, driver circuitry 1422, power management integrated circuit (PMIC) 1424, antenna structure 1426, and battery 1428.
  • the components of the UE 1400 may be implemented as integrated circuits (ICs) , portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof.
  • ICs integrated circuits
  • FIG. 14 is intended to show a high-level view of some of the components of the UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
  • the components of the UE 1400 may be coupled with various other components over one or more interconnects 1432, which may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
  • interconnects 1432 may represent any type of interface, input/output, bus (local, system, or expansion) , transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
  • the processors 1404 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1404A, central processor unit circuitry (CPU) 1404B, and graphics processor unit circuitry (GPU) 1404C.
  • the processors 1404 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 1412 to cause the UE 1400 to perform operations as described herein.
  • the baseband processor circuitry 1404A may access a communication protocol stack 1436 in the memory/storage 1412 to communicate over a 3GPP compatible network.
  • the baseband processor circuitry 1404A may access the communication protocol stack 1436 to: perform user plane functions at a PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layer; and perform control plane functions at a PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and a NAS layer.
  • the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 1408.
  • the baseband processor circuitry 1404A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks.
  • the waveforms for NR may be based cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
  • CP-OFDM cyclic prefix OFDM
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • the memory/storage 1412 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 1436) that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform various operations described herein.
  • the memory/storage 1412 include any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory/storage 1412 may be located on the processors 1404 themselves (for example, L1 and L2 cache) , while other memory/storage 1412 is external to the processors 1404 but accessible thereto via a memory interface.
  • the memory/storage 1412 may include 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.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read only memory
  • EEPROM electrically erasable programmable read only memory
  • Flash memory solid-state memory, or any other type of memory device technology.
  • SIM subscriber identity module
  • USB universal subscriber identity module
  • the UE 1400 may include a universal integrated circuit card (UICC) that is removably coupled with platform circuitry of the UE 1400 through, for example, a card slot.
  • the UICC may include portions of the processors 1404 and memory/storage 1412 and may include the SIM/USIM.
  • the components of the UICC may be integrated directly into (e.g., permanently coupled with) the platform circuitry of the UE 1400.
  • the RF interface circuitry 1408 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 1400 to communicate with other devices over a radio access network.
  • RFEM radio frequency front module
  • the RF interface circuitry 1408 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.
  • the RFEM may receive a radiated signal from an air interface via antenna structure 1426 and proceed to filter and amplify (with a low-noise amplifier) the signal.
  • the signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 1404.
  • the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM.
  • the RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna structure 1426.
  • the RF interface circuitry 1408 may be configured to transmit/receive signals in a manner compatible with NR access technologies.
  • the antenna structure 1426 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals.
  • the 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 communications.
  • the antenna structure 1426 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas.
  • the antenna structure 1426 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
  • the user interface 1416 includes various input/output (I/O) devices designed to enable user interaction with the UE 1400.
  • the user interface 1416 includes input device circuitry and output device circuitry.
  • Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like.
  • the output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information.
  • Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, and projectors) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 1400.
  • simple visual outputs/indicators for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs) , LED displays, quantum dot displays, and projectors)
  • LCDs liquid crystal displays
  • LED displays for example, LED displays, quantum dot displays, and projectors
  • the sensors 1420 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, or subsystem.
  • sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other like audio capture devices.
  • the driver circuitry 1422 may include software and hardware elements that operate to control particular devices that are embedded in the UE 1400, attached to the UE 1400, or otherwise communicatively coupled with the UE 1400.
  • the driver circuitry 1422 may include individual drivers allowing other components to interact with or control various I/O devices that may be present within, or connected to, the UE 1400.
  • the driver circuitry 1422 may include circuitry to facilitate coupling of a UICC (for example, UICC 148) to the UE 1400.
  • driver circuitry 1422 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 1420 and control and allow access to sensors 1420, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface
  • sensor drivers to obtain sensor readings of sensors 1420 and control and allow access to sensors 1420
  • drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers to control and allow access to one or more audio devices.
  • the PMIC 1424 may manage power provided to various components of the UE 1400.
  • the PMIC 1424 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC 1424 may control, or otherwise be part of, various power saving mechanisms of the UE 1400 including DRX as discussed herein.
  • a battery 1428 may power the UE 1400, although in some examples the UE 1400 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery 1428 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 1428 may be a typical lead-acid automotive battery.
  • FIG. 15 illustrates a network node 1500 in accordance with some embodiments.
  • the network node 1500 may be similar to and substantially interchangeable with base station 108, a device implementing one of the network hops 154, an IAB node, a network-controlled repeater, or a server in a core network or external data network.
  • the network node 1500 may include processors 1504, RF interface circuitry 1508 (if implemented as an access node) , core network (CN) interface circuitry 1512, memory/storage circuitry 1516, and antenna structure 1526.
  • the components of the network node 1500 may be coupled with various other components over one or more interconnects 1528.
  • the processors 1504, RF interface circuitry 1508, memory/storage circuitry 1516 (including communication protocol stack 1510) , antenna structure 1526, and interconnects 1528 may be similar to like-named elements shown and described with respect to FIG. 14.
  • the CN interface circuitry 1512 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol.
  • Network connectivity may be provided to/from the network node 1500 via a fiber optic or wireless backhaul.
  • the CN interface circuitry 1512 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols.
  • the CN interface circuitry 1512 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
  • the network node 1500 may be coupled with transmit receive points (TRPs) using the antenna structure 1526, CN interface circuitry, or other interface circuitry.
  • TRPs transmit receive points
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 includes a method comprising: receiving information to associate eight TCI codepoints with respective combinations of four TCI states; receiving downlink control information (DCI) having a three-bit value in a transmission configuration indicator (TCI) codepoint field to indicate a first TCI codepoint of the eight TCI codepoints, wherein the first TCI codepoints is configured with a first combination of four TCI states; and processing an uplink or downlink transmission based on one or more TCI states from the first combination of four TCI states.
  • DCI downlink control information
  • TCI transmission configuration indicator
  • Example 2 includes the method of example 1 or some other example herein, 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 method further comprises: 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.
  • Example 3 includes the method of example 1 or some other example herein, wherein the DCI further includes a two-bit value in an application field and the method further comprises: determining whether to update a first downlink TCI state to a first TCI state of the four TCI states and whether to update a second downlink TCI state to a second TCI state of the four TCI states based on a first bit of the two-bit value; and determining whether to update a first uplink TCI state to a third TCI state of the four TCI states and whether to update a second uplink TCI state to a fourth TCI state of the four TCI states based on a second bit of the two-bit value.
  • Example 4 includes a method of example 1 or some other example herein, wherein the DCI further includes a two-bit value in an application field and the method further comprises: determining whether to update a first downlink TCI state to a first TCI state of the four TCI states and whether to update a first uplink TCI state to a second TCI state of the four TCI states based on a first bit of the two-bit value; and determining whether to update a second downlink TCI state to a third TCI state of the four TCI states and whether to update a second uplink TCI state to a fourth TCI state of the four TCI states based on a second bit of the two-bit value.
  • Example 5 includes a method comprising: receiving a first media access control (MAC) control element (CE) having a first list identifier (ID) and a first plurality of transmission 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.
  • MAC media access control
  • CE control element
  • ID list identifier
  • TCI transmission configuration indicator
  • Example 6 includes the method of example 5 or some other example herein, wherein the method further comprises: receiving a downlink control information (DCI) having a first three-bit value in a first TCI codepoint field and a second three-bit value in a second TCI codepoint field; and identifying first one or more TCI states from the first TCI-state list based on the first three-bit value; and identifying second one or more TCI states from the second TCI-state list based on the second three-bit value.
  • DCI downlink control information
  • Example 7 includes a method of example 6 or some other example herein, wherein the DCI comprises DCI format 1_1 or DCI format 1_2 with or without data scheduling.
  • Example 8 includes the method of example 5 or some other example herein, wherein the method further comprises: receiving a downlink control information (DCI) having a first value in a set field and a second value in a TCI codepoint field, wherein the first value is a one-bit or 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.
  • DCI downlink control information
  • Example 9 includes a method of example 8 or some other example herein, wherein the first value is a one-bit value, said selecting comprises selecting one indicated list from the first TCI-state list and the second TCI-state list based on the first value, and said identifying the at least one TCI state comprises identifying at least one TCI state from the one indicated list.
  • Example 10 includes the method of example 8 or some other example herein, wherein the first value is a two-bit value, and said selecting the one or more indicated lists comprises: determining whether the first TCI-state 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-state list is included in the one or more indicated lists based on a second bit of the two-bit value.
  • Example 11 includes the method of 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.
  • TRP transmit-receive point
  • Example 12 includes a method comprising: transmitting a first media access control (MAC) control element (CE) having a first list identifier (ID) and a first plurality of transmission configuration indicator (TCI) state identifiers to configure a first TCI-state list; and transmitting a second MAC CE having a second list ID and a second plurality of TCI state identifiers to configure a second TCI-state list.
  • MAC media access control
  • CE control element
  • ID list identifier
  • TCI transmission configuration indicator
  • Example 13 includes the method of example 12 or some other example herein, wherein the method further comprises: transmitting a downlink control information (DCI) having a first three-bit value in a first TCI codepoint field and a second three-bit value in a second TCI codepoint field, wherein the first three-bit value is to identify first one or more TCI states from the first TCI-state and the second three-bit value is to identify second one or more TCI states from the second TCI-state list.
  • DCI downlink control information
  • Example 14 includes the method of example 13 or some other example herein, wherein the DCI comprises DCI format 1_1 or DCI format 1_2 with or without data scheduling.
  • Example 15 includes a method comprising: identifying two unified downlink transmission configuration indicator (TCI) states associated with a TCI codepoint; determining one or both of the two unified downlink TCI states are to be used as default TCI state (s) ; and receiving a physical downlink shared channel (PDSCH) transmission based on the default TCI state (s) .
  • TCI transmission configuration indicator
  • Example 16 includes the method of example 15 or some other example herein, further comprising: receiving a radio resource control (RRC) parameter in a control resource set (CORESET) configuration or a PDSCH configuration; and determining one or both of the two unified downlink TCI states are to be used as default TCI state (s) based on the RRC parameter.
  • RRC radio resource control
  • Example 17 includes the method of example 16 or some other example herein, further comprising: receiving downlink control information (DCI) to schedule the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state (s) configured by the RRC parameter.
  • DCI downlink control information
  • Example 18 includes the method of example 15 or some other example herein, further comprising: receiving downlink control information (DCI) to schedule the PDSCH transmission; and receiving the PDSCH transmission based on the default TCI state (s) based on a determination that a time between receiving the DCI and receiving the PDSCH transmission is less than a predetermined threshold.
  • DCI downlink control information
  • Example 19 includes the method of example 18 or some other example herein, further comprising: transmitting, in a UE capability report, an indication of the predetermined threshold.
  • Example 20 includes the method of example 19 or some other example herein, wherein the predetermined threshold is associated with a subcarrier spacing (SCS) .
  • SCS subcarrier spacing
  • Example 21 includes the method of example 15 or some other example herein, further comprising: determining a quasi-co-location (QCL) assumption of a lowest control resource set (CORESET) identity (ID) ; and determining one or both of the two unified downlink TCI states are to be used as default TCI state (s) based on the QCL assumption of the lowest CORESET identity.
  • QCL quasi-co-location
  • Example 22 includes the method of example 15 or some other example herein, 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 is to be used in determining the default TCI state (s) , wherein the first mode is based on an RRC parameter in a control resource set (CORESET) configuration or a PDSCH configuration and the second mode is based on one or more TCI states used to monitor a control resource set (CORESET) .
  • RRC radio resource control
  • Example 23 includes a method of example 15 or some other example herein, wherein the PDSCH transmission is a first PDSCH transmission and the method further comprises: receiving a downlink control information (DCI) to schedule a second PDSCH transmission, the DCI to include a TCI codepoint field to indicate one or both of the two unified downlink TCI states; and determining one or both of the two unified downlink TCI states are to be used as default TCI state (s) based on the TCI codepoint field, wherein the first PDSCH transmission is to occur after the second PDSCH transmission.
  • DCI downlink control information
  • Example 24 includes a method of example 23 or some other example herein, further comprising: receiving the first PDSCH transmission after a time period that is greater than a time duration for quasi-colocation (QCL) from receiving the DCI.
  • QCL quasi-colocation
  • Another example may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1–23, or any other method or process described herein.
  • Another example may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1–23, or any other method or process described herein.
  • Another example may include a method, technique, or process as described in or related to any of examples 1–23, or portions or parts thereof.
  • Another example may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–23, or portions thereof.
  • Another example include a signal as described in or related to any of examples 1–23, or portions or parts thereof.
  • Another example may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1–23, or portions or parts thereof, or otherwise described in the present disclosure.
  • Another example may include a signal encoded with data as described in or related to any of examples 1–23, or portions or parts thereof, or otherwise described in the present disclosure.
  • Another example may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1–23, or portions or parts thereof, or otherwise described in the present disclosure.
  • Another example may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1–23, or portions thereof.
  • Another example may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1–23, or portions thereof.
  • Another example may include a signal in a wireless network as shown and described herein.
  • Another example may include a method of communicating in a wireless network as shown and described herein.
  • Another example may include a system for providing wireless communication as shown and described herein.
  • Another example may include a device for providing wireless communication as shown and described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande propose des dispositifs et des composants comprenant des appareils, des systèmes et des procédés d'association d'indicateur de configuration de transmission pour une réception de canal physique partagé descendant.
PCT/CN2022/129574 2022-11-03 2022-11-03 Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant WO2024092623A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129574 WO2024092623A1 (fr) 2022-11-03 2022-11-03 Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129574 WO2024092623A1 (fr) 2022-11-03 2022-11-03 Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant

Publications (1)

Publication Number Publication Date
WO2024092623A1 true WO2024092623A1 (fr) 2024-05-10

Family

ID=90929301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129574 WO2024092623A1 (fr) 2022-11-03 2022-11-03 Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant

Country Status (1)

Country Link
WO (1) WO2024092623A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200267734A1 (en) * 2019-02-15 2020-08-20 Qualcomm Incorporated Methods and apparatus for pdsch tci states activation-deactivation in multi-trp
EP3897057A1 (fr) * 2019-02-15 2021-10-20 Huawei Technologies Co., Ltd. Procédé et appareil d'indication d'informations
CN113767697A (zh) * 2021-08-05 2021-12-07 北京小米移动软件有限公司 一种传输配置指示tci状态配置的方法及其装置
US20220294509A1 (en) * 2021-03-11 2022-09-15 Comcast Cable Communications, Llc Beam Activation and Determination in Wireless Networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200267734A1 (en) * 2019-02-15 2020-08-20 Qualcomm Incorporated Methods and apparatus for pdsch tci states activation-deactivation in multi-trp
EP3897057A1 (fr) * 2019-02-15 2021-10-20 Huawei Technologies Co., Ltd. Procédé et appareil d'indication d'informations
US20220294509A1 (en) * 2021-03-11 2022-09-15 Comcast Cable Communications, Llc Beam Activation and Determination in Wireless Networks
CN113767697A (zh) * 2021-08-05 2021-12-07 北京小米移动软件有限公司 一种传输配置指示tci状态配置的方法及其装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Remaining update for PDSCH TCI state MAC CE", 3GPP TSG-RAN WG2 MEETING #109 ELECTRONIC TDOC R2-2001126, 13 February 2020 (2020-02-13), XP051848743 *

Similar Documents

Publication Publication Date Title
WO2022021356A1 (fr) Réduction de complexité d'équipement utilisateur pour réception de répétition de canal de commande de liaison descendante physique
WO2022082351A1 (fr) Transmission de signal de référence de suivi de phase pour l'amélioration de la fiabilité de canal partagé de liaison montante physique
US20220304036A1 (en) Unsynchronized multi-transmission reception point scheduling operation
US20220304023A1 (en) Transmission configuration indication and transmission occasion mapping
WO2022073209A1 (fr) Adaptation de débit pour une opération intercellulaire avec plusieurs points d'émission-réception
WO2022082359A1 (fr) Répétition de canal physique partagé montant avec différentes configurations
US20220312485A1 (en) Spatial collision handling for multiple transmit and receive point operation
US20220303807A1 (en) Parallel beam management in new band combinations
WO2024092623A1 (fr) Technologies d'association d'indicateur de configuration de transmission pour réception de canal physique partagé descendant
US20240107523A1 (en) Antenna port indication for more than four layer physical uplink shared channel operation
US20240057140A1 (en) Phase tracking reference signal user equipment capability reporting
US20240056341A1 (en) Phase tracking reference signal configuration
US20240031948A1 (en) Power headroom reporting for multi-beam uplink transmissions
WO2023004581A1 (fr) Réduction de latence pour reprise après défaillance de faisceau
US20230345395A1 (en) Measurement opportunity sharing for layer one measurements
US20230379754A1 (en) Ad-hoc radio bearer and inline signalling via reflective quality of service
US20240048345A1 (en) Unified transmission configuration indicator state selection for physical downlink shared channel or physical uplink shared channel transmissions
US20240057069A1 (en) Configured grant simultaneous multi-panel transmission
US20240048339A1 (en) Unified transmission configuration indicator state selection for channel state information reference signal transmissions
US20240057056A1 (en) Network bandwidth adjustment and indication
US20230217379A1 (en) Technologies for power headroom reporting for transmit/receive points
US20240205923A1 (en) User equipment aggregation for uplink communications
WO2022151046A1 (fr) Attribution de ressources de fréquence pour de nouveaux services de multidiffusion ou de diffusion radio
WO2023114089A1 (fr) Technologies dans des communications sans fil en tenant compte d'un véhicule à grande vitesse
WO2023211661A1 (fr) Transmission non basée sur livre de codes de signaux de référence de sondage