WO2023050272A1

WO2023050272A1 - Determining a resource configuration based on a list of component carriers

Info

Publication number: WO2023050272A1
Application number: PCT/CN2021/122093
Authority: WO
Inventors: Chenxi Zhu; Bingchao LIU; Yi Zhang; Wei Ling; Lingling Xiao
Original assignee: Lenovo (Beijing) Limited
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2023-04-06

Abstract

Apparatuses, methods, and systems are disclosed for determining a resource configuration based on a list of component carriers. One method (700) includes receiving (702) at least one first RRC message that configures at least one TCI state pool in at least one PDSCH configuration in at least one BWP and at least one CC. The method (700) includes receiving (704) at least one second RRC message that configures at least one list of CCs for sharing TCI state pools in the at least one BWP and the at least one CC. The method (700) includes determining (706) a reference BWP and a reference CC in response to a TCI state pool not being configured for a combination of a BWP having a BWP identifier and a CC having a CC identifier in the at least one list of CCs for sharing TCI state pools.

Description

DETERMINING A RESOURCE CONFIGURATION BASED ON A LIST OF COMPONENT CARRIERS

FIELD

The subject matter disclosed herein relates generally to wireless communications and more particularly relates to determining a resource configuration based on a list of component carriers.

BACKGROUND

In certain wireless communications networks, there may be multiple options for a device resource configuration. In such networks, the device may need to determine its resource configuration.

BRIEF SUMMARY

Methods for determining a resource configuration based on a list of component carriers are disclosed. Apparatuses and systems also perform the functions of the methods. In one embodiment, the method includes receiving, at a user equipment, at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier. In certain embodiments, the method includes receiving at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier. In some embodiments, the method includes determining a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

An apparatus for determining a resource configuration based on a list of component carriers, in one embodiment, includes a user equipment. In some embodiments, the apparatus includes a receiver that: receives at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and receives at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier. In various embodiments, the apparatus includes a processor that determines a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for determining a resource configuration based on a list of component carriers;

Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for determining a resource configuration based on a list of component carriers;

Figure 3 is a schematic block diagram illustrating another embodiment of an apparatus that may be used for determining a resource configuration based on a list of component carriers;

Figure 4 is a table of one embodiment of a configuration of a TCI state pool in BWPs and/or CC in a CC list with 4 component carriers;

Figure 5 is a table illustrating one example of a reference BWP and a reference CC of a TCI state pool according to a first embodiment;

Figure 6 is a table illustrating one example of a reference BWP and a reference CC of a TCI state pool according to a second embodiment; and

Figure 7 is a schematic flow chart diagram illustrating one embodiment of a method for determining a resource configuration based on a list of component carriers.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit, ” “module” or “system. ” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration ( “VLSI” ) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ( “RAM” ) , a read-only memory ( “ROM” ) , an erasable programmable read-only memory ( “EPROM” or Flash memory) , a portable compact disc read-only memory ( “CD-ROM” ) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ( “LAN” ) or a wide area network ( “WAN” ) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment, ” “an embodiment, ” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment, ” “in an embodiment, ” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including, ” “comprising, ” “having, ” and variations thereof mean “including but not limited to, ” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a, ” “an, ” and “the” also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

Figure 1 depicts an embodiment of a wireless communication system 100 for determining a resource configuration based on a list of component carriers. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants ( “PDAs” ) , tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, modems) , IoT devices, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user equipment ( “UE” ) , user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via uplink ( “UL” ) communication signals and/or the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNodeB ( “gNB” ) , a Home Node-B, a RAN, a relay node, a device, a network device, an integrated and access backhaul ( “IAB” ) node, a donor IAB node, a controller, a RIS device, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 is compliant with the 5G or NG (Next Generation) standard of the third generation partnership program ( “3GPP” ) protocol, wherein the network unit 104 transmits using NG RAN technology. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit downlink ( “DL” ) communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

In various embodiments, a remote unit 102 may receive at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier. In certain embodiments, the remote unit 102 may receive at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier. In some embodiments, the remote unit 102 may determine a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools. Accordingly, a remote unit 102 may be used for determining a resource configuration based on a list of component carriers.

Figure 2 depicts one embodiment of an apparatus 200 that may be used for determining a resource configuration based on a list of component carriers. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit ( “CPU” ) , a graphics processing unit ( “GPU” ) , an auxiliary processing unit, a field programmable gate array ( “FPGA” ) , or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM ( “DRAM” ) , synchronous dynamic RAM ( “SDRAM” ) , and/or static RAM ( “SRAM” ) . In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display ( “LCD” ) display, an LED display, an organic light emitting diode ( “OLED” ) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime) . In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

In some embodiments, the receiver 212: receives at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and receives at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier. In various embodiments, the processor 202 determines a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

Figure 3 depicts another embodiment of an apparatus 300 that may be used for determining a resource configuration based on a list of component carriers. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

Although only one transmitter 310 and one receiver 312 are illustrated, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

In certain embodiments, a transmission configuration indicator ( “TCI” ) state may represent a downlink ( “DL” ) TCI, an uplink ( “UL” ) TCI, or a joint UL and DL TCI. In some embodiments, a TCI state pool may be configured, and a separate DL TCI state, UL TCI state, or joint DL and UL TCI state indicated by a TCI field in downlink control information ( “DCI” ) (e.g., DCI format 1_1, DCI format 1_2) with or without a physical downlink shared channel ( “PDSCH” ) assignment may be used to update the common TCI state for a PDSCH, a physical downlink control channel ( “PDCCH” ) , a physical uplink shared channel ( “PUSCH” ) , and/or a physical uplink control channel ( “PUCCH” ) , and some DL and UL reference signals ( “RSs” ) may share the same TCI state with the DL and/or UL channels. A radio resource control ( “RRC” ) configured TCI state pool may be present or absent in a bandwidth part ( “BWP” ) and/or component carrier ( “CC” ) . If RRC-configured TCI state pools are absent in a PDSCH configuration (e.g., PDSCH-Config) for each BWP and/or CC, another TCI state pool configured in a reference BWP and/or CC may be used in its place. For a BWP and/or CC where the PDSCH configuration contains a reference to the RRC-configured TCI state pools in a reference BWP and/or CC, a user equipment ( “UE” ) applies the RRC-configured TCI state pools in the reference BWP and/or CC. If the BWP and/or CC identifier ( “ID” ) for a quasi-co-location ( “QCL” ) Type ( “QCL-Type” ) A and/or D source reference signal ( “RS” ) in a QCL information ( “QCL-Info” ) of the TCI state is absent, the UE assumes that QCL-Type A and/or D source RSs are in the BWP and/or CC to which the TCI state applies. In some embodiments, there may be various methods for determining a reference BWP and/or CC in a configured list of CCs.

In various embodiments, there may be methods of configuring a TCI state pool in a RRC across a set of component carriers. In such embodiments, a list of CCs may be updated using a medium access control ( “MAC” ) control element ( “CE” ) ( “MAC-CE” ) . In certain embodiments, two types of CC lists may be defined for updating TCI states in multiple CCs, one for DL TCI and one for UL spatial relation information.

In certain embodiments, such as for DL, two lists of CCs (e.g., simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16) may be defined in RRC for simultaneously updating TCI codepoints for PDSCH in all CCs in the lists. If a set of TCI state identifiers ( “IDs” ) are activated for a set of CCs and/or DL BWPs, using TCI states activation and/or deactivation for a UE-specific PDSCH MAC CE or an enhanced TCI states activation and/or deactivation for the UE-specific PDSCH MAC CE, the same set of TCI state IDs may be applied for all DL BWPs in the indicated CCs. The list of CCs may also be used to indicate the TCI state for PDCCH for all the CCs in the list. If a UE receives a TCI state indication for UE-specific PDCCH MAC CE, and the indicated serving cell is part of a list (e.g., simultaneousTCI-UpdateList1-r16 or simultaneousTCI-UpdateList2-r16) , all the PDCCH in the list may be assigned the TCI state signaled in the MAC-CE.

In some embodiments, such as for UL, two lists of CCs (e.g., simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) , may be defined in RRC for simultaneously updating the spatial relation for sounding reference signal ( “SRS” ) resources. If an indicated serving cell is part of a list (e.g., simultaneousSpatial-UpdatedList1 or simultaneousSpatial-UpdatedList2) and the UL spatial relation signaled in the serving cell set based SRS spatial relation indication, the MAC CE may apply to all the serving cells configured in the lists (e.g., simultaneousSpatial-UpdatedList1 or simultaneousSpatial-UpdatedList2) . All the SRS resources with the same SRS resource ID in the CCs in the same list may have the same UL spatial relation.

In various embodiments, because different lists of CCs (e.g., simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16, and simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) apply to DL and UL separately, a network may configure them to be different. This may give the network the flexibility to group different sets of CCs for simultaneous TCI and/or spatial relation information update in the DL and UL. In certain embodiments, a TCI state may be a DL-only TCI, an UL-only TCI, or a joint DL and UL TCI state, and there may be no mechanism to dynamically switch between them. If a UE is RRC configured with joint DL and UL TCI states, the TCI states may apply to multiple CCs in both DL and UL. In certain embodiments, for DL, CCs in lists (e.g., simultaneousTCI-UpdateList1- r16 and simultaneousTCI-UpdateList2-r16) may only share activated TCI state numbers, while the TCI state pools may be individually configured for each BWP and/or CC. This may imply that the TCI states indicated by DCI (e.g., DCI format 1_1 and/or DCI format 1_2) with the same TCI state ID may still be different in different CCs, provided the TCI state pools configured in PDSCH-Config in different CCs are different.

In some embodiments, a CC list in RRC for shared TCI state pool configurations may be used. The CC list may include a mixture of DL-only TCI states, UL-only TCI states, and joint DL and UL TCI states. As an example, two lists (e.g., simultaneousUnifiedTCI-UpdateList1-r17 and simultaneousUnifiedTCI-UpdateList2-r17) may be used. In various embodiments, lists (e.g., simultaneousTCI-UpdateList1 and/or simultaneousTCI-UpdateList2) may be used.

In various embodiments, for a BWP and/or CC of a CC in a list with its own TCI state pool configured (e.g., in the PDSCH-Config) , a TCI state pool may be used in the BWP and/or CC disregarding the TCI state pools configured in other BWPs or in other CCs in the same list. In certain embodiments, for a BWP and/or CC in a list, if there is no RRC configured TCI state pool (e.g., in its PDSCH-Config) , a TCI state pool configured in a reference BWP and/or CC in the same CC list may be used.

In some embodiments, for a BWP and/or CC of a CC in a list, if it does not have its own TCI state pool configured (e.g., in its PDSCH-Config) , the following may be used to define a reference BWP and/or CC: 1) in a first embodiment, if there is at least one other BWP of the same CC which has a TCI state pool configured (e.g., in the PDSCH-Config) , this TCI state pool may be used for this target BWP -if there is more than one BWP in the same cell with TCI state pools configured (e.g., in their PDSCH-Config) , the TCI state pool of the BWP with a lower BWP ID may be used, and if there is no BWP of the same CC configured with a TCI state pool (e.g., in the PDSCH-Config) , the TCI state pool configured (e.g., in the PDSCH-Config) for a reference BWP and/or CC may be used -the reference CC may be the CC with the lowest cell ID in the same CC list that has a TCI state pool configured (e.g., in the PDSCH-Config) in at least one BWP -if there is more than one BWP in this CC that has TCI state pools configured (e.g., in the PDSCH-Config) , the BWP with the lowest BWP ID may be used -in other words, this TCI state pool is used in all the BWPs of those CCs that have no TCI state pool configured in any of their BWPs; and 2) in a second embodiment, a TCI state pool is derived from a reference BWP in a reference CC in the same CC list. The reference CC may be the CC with the lowest CC index in the same list that has a TCI state pool configured (e.g., in the PDSCH-Config) in at least one BWP. If there is more than one BWP in this CC that has TCI state pools configured (e.g., in the PDSCH-Config) , the TCI state pool of the BWP with the lowest BWP ID is used.

In a first example, a UE is configured with 3 component carriers (cells) , each with 4 BWPs. TCI state pools are configured for only a subset of the BWPs and CCs as shown in Figure 4. Specifically, Figure 4 is a table 400 of one embodiment of a configuration of a TCI state pool in BWPs and/or CC in a CC list (e.g., simultaneousUnifiedTCI-UpdateList CC list) with 4 component carriers. In Figure 4, Y indicates that a TCI-state pool is configured (e.g., in the PDSCH-Config) of the combined BWP and CC, while an N indicates that a TCI-state pool is not configured (e.g., in the PDSCH-Config) of the combined BWP and CC.

In various embodiments, a UE ends up with different TCI state pools for CCs and/or BWPs with the first and second embodiments. With the first embodiment, priority may be given to a TCI state pool configured in the same CC, if possible. One benefit of the first embodiment may be that different BWPs of the same CC are more likely to share the same TCI state pool, and if a TCI state in the TCI state pool contains a RS with QCL-TypeA, it is also used as QCL-TypeA RS in the other BWPs of the same CC. Because a QCL-TypeA RS is in the same carrier as the target channel or RS, it loses its significance when the TCI is reused in a different carrier. If the first embodiment is used for the configuration of Figure 4, the reference BWP and CC for each BWP and CC is shown in Figure 5. Figure 5 is a table 500 illustrating one example of a reference BWP and a reference CC of a TCI state pool according to the first embodiment.

In the second embodiment, the reference BWP and CC (e.g., BWP1 and CC1) is the same for all the BWPs and CCs that do not have TCI state pool configured (e.g., in their own PDSCH-Config) . If a TCI state in the TCI state pool configured in BWP1 and CC1 has a RS with QCL-TypeA, this QCL-TypeA RS has to be dropped for those BWPs in CC2, CC3, and CC4. For example, if a TCI state in BWP1 and CC1 has two reference signals with different QCL types as shown in Table 1, where qcl-Type1 RS is a NZP-CSI-RS (e.g., first CSI-RS resource) as QCL-TypeA, and qcl-Type2 RS is another NZP-CSI-RS (e.g., second CSI-RS resource) as QCL-TypeD, only the second CSI-RS resource as QCl-TypeD is used if the TCI state is used in CC2, CC3, and CC4. Figure 6 shows one example of using the second embodiment in which the reference BWP and CC are illustrated for each BWP and CC. Specifically, Figure 6 is a table 600 illustrating one example of a reference BWP and a reference CC of a TCI state pool according to the second embodiment.

Table 1

If the number of the TCI states in the TCI state pool (or in the TCI state pool in the reference BWP and CC) is larger than the number of TCI states that can be signaled by the TCI bits in DCI (e.g., DCI format 1_1, DCI format 1_2) (8 states corresponding to 3 TCI bits) , a MAC-CE may be used to activate a subset of the TCI states for use in the BWPs and CCs. A TCI state activation and/or deactivation for UE-specific PDSCH MAC-CE or an enhanced TCI state activation and/or deactivation for UE-specific PDSCH MAC-CE may be used.

Figure 7 is a schematic flow chart diagram illustrating one embodiment of a method 700 for determining a resource configuration based on a list of component carriers. In some embodiments, the method 700 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 700 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 700 may include receiving 702 at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier. In certain embodiments, the method 700 includes receiving 704 at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier. In some embodiments, the method 700 includes determining 706 a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

In certain embodiments, the reference bandwidth part and the reference component carrier are determined first based on bandwidth parts of the at least one bandwidth part of a same component carrier in the at least one list of component carriers as the component carrier having the component carrier identifier, then based on the bandwidth parts of the at least one bandwidth part of different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier. In some embodiments, the reference bandwidth part and the reference component carrier are determined first based on the bandwidth parts of the at least one bandwidth part in the same component carrier configured with a transmission configuration indicator state pool having a lowest identifier. In various embodiments, a component carrier having a lower identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier is checked before a component carrier having a higher identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.

In one embodiment, the reference bandwidth part and the reference component carrier are determined first based on different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier, then based on bandwidth parts of the at least one bandwidth part of the component carrier having the component carrier identifier. In certain embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools is different from at least one list of component carriers for a simultaneous transmission configuration indicator state update in downlink, and at least one list of component carriers for a simultaneous spatial relation update in uplink. In some embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools comprises a first simultaneous transmission configuration indicator update list and a second simultaneous transmission configuration indicator update list.

In various embodiments, in response to a reference transmission configuration indicator state being defined in another component carrier and having a QCL-TypeA reference signal, the QCL-TypeA reference signal is not used in the target component carrier. In one embodiment, the reference bandwidth part and the reference component carrier are determined based first on a bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier and then on a component carrier of the at least one component carrier having a lowest component carrier identifier. In certain embodiments, the reference bandwidth part and the reference component carrier are determined based first on a component carrier of the at least one component carrier having a lowest component carrier identifier and then on a bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier.

In one embodiment, a method of a user equipment comprises: receiving at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; receiving at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and determining a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

In certain embodiments, the reference bandwidth part and the reference component carrier are determined first based on bandwidth parts of the at least one bandwidth part of a same component carrier in the at least one list of component carriers as the component carrier having the component carrier identifier, then based on the bandwidth parts of the at least one bandwidth part of different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.

In some embodiments, the reference bandwidth part and the reference component carrier are determined first based on the bandwidth parts of the at least one bandwidth part in the same component carrier configured with a transmission configuration indicator state pool having a lowest identifier.

In various embodiments, a component carrier having a lower identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier is checked before a component carrier having a higher identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.

In one embodiment, the reference bandwidth part and the reference component carrier are determined first based on different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier, then based on bandwidth parts of the at least one bandwidth part of the component carrier having the component carrier identifier.

In certain embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools is different from at least one list of component carriers for a simultaneous transmission configuration indicator state update in downlink, and at least one list of component carriers for a simultaneous spatial relation update in uplink.

In some embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools comprises a first simultaneous transmission configuration indicator update list and a second simultaneous transmission configuration indicator update list.

In various embodiments, in response to a reference transmission configuration indicator state being defined in another component carrier and having a QCL-TypeA reference signal, the QCL-TypeA reference signal is not used in the target component carrier.

In one embodiment, the reference bandwidth part and the reference component carrier are determined based first on a bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier and then on a component carrier of the at least one component carrier having a lowest component carrier identifier.

In certain embodiments, the reference bandwidth part and the reference component carrier are determined based first on a component carrier of the at least one component carrier having a lowest component carrier identifier and then on a bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier.

In one embodiment, an apparatus comprises a user equipment. The apparatus further comprises: a receiver that: receives at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and receives at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and a processor that determines a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

In some embodiments, a method of a network device comprises: transmitting at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; transmitting at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and receiving a transmission on a reference bandwidth part and a reference component carrier, wherein the reference bandwidth part and the reference component carrier are determined in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

In various embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools is configured using radio resource control signaling.

In one embodiment, an apparatus comprises a network device. The apparatus further comprises a transmitter that: transmits at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and transmits at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and a receiver that receives a transmission on a reference bandwidth part and a reference component carrier, wherein the reference bandwidth part and the reference component carrier are determined in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.

In certain embodiments, the at least one list of component carriers for sharing transmission configuration indicator state pools is configured using radio resource control signaling.

Embodiments may be practiced in other specific forms. One or more of the embodiments described herein may be combined to form another embodiment. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

A method of a user equipment, the method comprising:

receiving at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier;

receiving at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and

determining a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.
The method of claim 1, wherein the reference bandwidth part and the reference component carrier are determined first based on configured bandwidth parts of the at least one bandwidth part of a same component carrier in the at least one list of component carriers as the component carrier having the component carrier identifier, then based on the configured bandwidth parts of the at least one bandwidth part of different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.
The method of claim 2, wherein the reference bandwidth part and the reference component carrier are determined first based on the configured bandwidth parts of the at least one bandwidth part in the same component carrier configured with a transmission configuration indicator state pool having a lowest identifier.
The method of claim 3, wherein a component carrier having a lower identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier is checked before a component carrier having a higher identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.
The method of claim 1, wherein, in response to a reference transmission configuration indicator state being defined in another component carrier and having a QCL-TypeA reference signal, the QCL-TypeA reference signal is not used in the target component carrier.
The method of claim 1, wherein the reference bandwidth part and the reference component carrier are determined based first on a configured component carrier of the at least one component carrier having a lowest component carrier identifier and then on a configured bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier.
An apparatus comprising a user equipment, the apparatus further comprising:

a receiver that:

receives at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and

receives at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and

a processor that determines a reference bandwidth part and a reference component carrier in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.
The apparatus of claim 7, wherein the reference bandwidth part and the reference component carrier are determined first based on configured bandwidth parts of the at least one bandwidth part of a same component carrier in the at least one list of component carriers as the component carrier having the component carrier identifier, then based on the configured bandwidth parts of the at least one bandwidth part of different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.
The apparatus of claim 8, wherein the reference bandwidth part and the reference component carrier are determined first based on the configured bandwidth parts of the at least one bandwidth part in the same component carrier configured with a transmission configuration indicator state pool having a lowest identifier.
The apparatus of claim 9, wherein a component carrier having a lower identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier is checked before a component carrier having a higher identifier of the different component carriers in the at least one list of component carriers different from the component carrier having the component carrier identifier.
The apparatus of claim 7, wherein the at least one list of component carriers for sharing transmission configuration indicator state pools is different from at least one list of component carriers for a simultaneous transmission configuration indicator state update in downlink, and at least one list of component carriers for a simultaneous spatial relation update in uplink.
The apparatus of claim 7, wherein, in response to a reference transmission configuration indicator state being defined in another component carrier and having a QCL-TypeA reference signal, the QCL-TypeA reference signal is not used in the target component carrier.
The apparatus of claim 7, wherein the reference bandwidth part and the reference component carrier are determined based first on a component carrier of the at least one component carrier having a lowest component carrier identifier and then on a bandwidth part of the at least one bandwidth part having a lowest bandwidth part identifier.
An apparatus comprising a network device, the apparatus further comprising:

a transmitter that:

transmits at least one first radio resource configuration message that configures at least one transmission configuration indicator state pool in at least one physical downlink shared channel configuration in at least one bandwidth part and at least one component carrier; and

transmits at least one second radio resource configuration message that configures at least one list of component carriers for sharing transmission configuration indicator state pools in the at least one bandwidth part and the at least one component carrier; and

a receiver that receives a transmission on a reference bandwidth part and a reference component carrier, wherein the reference bandwidth part and the reference component carrier are determined in response to a transmission configuration indicator state pool not being configured for a combination of a bandwidth part having a bandwidth part identifier and a component carrier having a component carrier identifier in the at least one list of component carriers for sharing transmission configuration indicator state pools.
The apparatus of claim 14, wherein the at least one list of component carriers for sharing transmission configuration indicator state pools is configured using radio resource control signaling.