Capability signaling for downlink and uplink carriers and cells in different frequency bands

Abstract

Methods, systems, and devices for wireless communication are described. A network node may send capability information indicating the capability of the network node to communicate using a pair of uplink and downlink carriers in a different frequency band or the same frequency band. The network node may receive carrier information based on the capability information, the carrier information indicating one or more downlink carriers and one or more uplink carriers including uplink and downlink carrier pairs for wireless communication. If the frequency band is the same for the uplink and downlink carriers, the carrier information may include second carrier information associated with another uplink carrier (e.g., an enhanced supplemental uplink (eSUL) carrier). A network node may participate in wireless communications using one of a downlink carrier and an uplink carrier.

Description

[0001] Cross-references

[0002] This patent application claims priority to PCT patent application No. PCT / CN2023 / 087464, filed April 11, 2023, entitled “A FRAMEWORK FORSUPPLEMENTARY UPLINK AND UPLINK CARRIER AGGREGATION”, and assigned to the assignee of this application. PCT patent application No. PCT / CN2023 / 087464 is expressly and entirely incorporated herein by reference.

[0003] introduction

[0004] The following discussion pertains to wireless communications relating to downlink and uplink carriers and cells in different frequency bands, and also to supplementary uplink (SUL) and uplink carrier aggregation (CA).

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting capability signaling for downlink and uplink carriers and cells in different or the same frequency band. In some aspects, a user equipment (UE) may indicate the capability to communicate using uplink-downlink carrier pairs via uplink and downlink cells, wherein the uplink and downlink carriers are used in different frequency bands or in the same frequency band. The UE may receive carrier information based on this capability, indicating one or more uplink and downlink carriers for which the UE intends to use wireless communication. In some aspects, the uplink carriers indicated in the carrier information may include a normal uplink carrier or normal cell, and a supplementary uplink (SUL) (or enhanced SUL (eSUL)) carrier or cell. Where the UE is capable of communicating using uplink-downlink carrier pairs in the same frequency band, the carrier information may include second carrier information based on this capability and based on the fact that the normal uplink carrier and the eSUL carrier are in the same frequency band. The UE may use indicated downlink and uplink carriers in the same or different frequency bands, or indicated downlink and eSUL carriers in the same or different frequency bands, to participate in wireless communication.

[0007] In some aspects, to support the framework for SUL and uplink carrier aggregation (CA), network entities can send broadcast or dedicated messages to the UE instructing (configuring to the UE) the uplink and downlink carrier pairs of the cell and one or more additional uplink carriers, which can be SUL carriers or enhanced SUL carriers (eSUL carriers). The UE can use the additional uplink carriers as SUL carriers when in idle mode, or as component carriers of CA when in connected mode. For example, when the UE determines the cell to access (when in idle mode), the UE can select or determine a candidate carrier (an uplink carrier in a normal uplink-uplink-downlink carrier pair, or an SUL carrier) for performing a random access procedure. For example, if the UE selects an SUL carrier, the UE can use that SUL carrier to perform a 2-step or 4-step random access procedure. Based on successful contention resolution, the UE can enter connected mode and use one or more additional uplink carriers (as component carriers in CA) from the normal uplink carrier or additional uplink carriers to perform subsequent uplink transmissions. The UE can perform uplink transmissions using an additional uplink carrier or a normal uplink carrier, based on the carrier used for the random access procedure.

[0008] A method is described. The method may include: transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participating in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0009] A first network node for wireless communication is described. The first wireless node may include at least one communication interface and at least one processor coupled to the communication interface. The first network node may be configured to: transmit capability information indicating the first network node's ability to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; receive carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participate in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0010] Another apparatus is described. This apparatus may include: components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and components for participating in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0011] A non-transitory computer-readable medium having code stored thereon for wireless communication is described. When executed by a first network node, the code enables the first network node to: transmit capability information indicating the first network node's ability to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; receive carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participate in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0012] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band, and the capability of the first network node to communicate using the pair of carriers can be indicated by the first indication and the second indication.

[0013] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information includes: a first list of individual frequency bands, wherein a first network node supports both downlink and uplink communication via each of these individual frequency bands; and a second list of frequency band pairs, wherein for each pair, the first network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with the downlink communication via a second pair of components in the corresponding pair, and the first frequency band and the second frequency band may be one of the frequency band pairs included in the second list.

[0014] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information may indicate one or more first sets of features supported by a first network node and one or more second sets of features supported by the first network node, wherein individual sets of the one or more first sets of features may be associated with a corresponding downlink band in a second list of the band pair, individual sets of the one or more second sets of features may be associated with a corresponding uplink band in a second list of the band pair, and the capability information indicates one or more first sets of features and one or more second sets of features separate from a third set of features supported by the first network node and each associated with a corresponding individual band from the first list.

[0015] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information includes a list of individual frequency bands, wherein a first network node supports both downlink and uplink communication via each of these individual frequency bands, the list including an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list of individual frequency bands, and the second frequency band may be included in an additional set of these additional uplink frequency bands, the corresponding individual frequency band belonging to that additional uplink frequency band being the first frequency band.

[0016] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information may indicate one or more first sets of features supported by the first network node and each associated with a corresponding individual frequency band from the list, and the capability information may also indicate one or more second sets of features supported by the first network node and each associated with at least one uplink frequency band from a corresponding set of these additional uplink frequency band sets.

[0017] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the first frequency band may be a time division duplex (TDD) band, and the second frequency band may be a frequency division duplex (FDD) band or a SUL band.

[0018] In some aspects of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more downlink carriers include SDL carriers, and the first frequency band may be an SDL band that includes the SDL carriers.

[0019] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, receiving the carrier information may include operations, features, components, or instructions for: receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier that can be paired with the first uplink carrier; and receiving second information indicating a second resource for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers.

[0020] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, participation in wireless communication may include operations, features, components, or instructions for: determining a first candidate uplink carrier for a random access procedure from a set of multiple candidate uplink carriers when the first network node is in an idle mode; and determining a second candidate uplink carrier for uplink transmission from a set of multiple candidate uplink carriers when the first network node is in a connected mode.

[0021] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, idle mode and connected mode can be communication states of a first network node relative to a second network node, communication during connected mode can be on resources that can be allocated for use by the first network node, and communication during idle mode can be on resources that can be allocated for use by a common network node.

[0022] A method is described. The method may include: transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0023] A first network node for wireless communication is described. The first wireless node may include at least one communication interface and at least one processor coupled to the communication interface. The first network node may be configured to: transmit capability information indicating the first network node's ability to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; receive carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participate in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0024] Another apparatus is described. This apparatus may include: components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and components for participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0025] A non-transitory computer-readable medium having code stored thereon for wireless communication is described. When executed by a first network node, the code enables the first network node to: transmit capability information indicating its ability to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; receive carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participate in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0026] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band, and the capability of the first network node to communicate using the pair of carriers can be indicated by the first indication and the second indication.

[0027] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the second uplink carrier may be an SUL carrier when the first network node is in idle mode, and may be an uplink component carrier for CA when the first network node is in connected mode.

[0028] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, receiving the carrier information may include operations, features, components, or instructions for: receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier that can be paired with the first uplink carrier; and receiving second information indicating a second resource for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers.

[0029] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, participation in wireless communication may include operations, features, components, or instructions for: determining a first candidate uplink carrier for a random access procedure from a set of multiple candidate uplink carriers when the first network node is in an idle mode; and determining a second candidate uplink carrier for uplink transmission from a set of multiple candidate uplink carriers when the first network node is in a connected mode.

[0030] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, idle mode and connected mode can be communication states of a first network node relative to a second network node, communication during connected mode can be on resources that can be allocated for use by the first network node, and communication during idle mode can be on resources that can be allocated for use by a common network node.

[0031] In some aspects of the methods, apparatuses and nontransitory computer-readable media described herein, the first frequency band may be a TDD frequency band.

[0032] A method is described. The method may include: receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for the second network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participating in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0033] A first network node for wireless communication is described. The first wireless node may include at least one communication interface and at least one processor coupled to the communication interface. The first network node may be configured to: receive capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; transmit carrier information indicating one or more downlink carriers and one or more uplink carriers for the second network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participate in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0034] Another apparatus is described. This apparatus may include: components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for the second network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and components for participating in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0035] A non-transitory computer-readable medium having code stored thereon for wireless communication is described. When executed by a first network node, the code enables the first network node to: receive capability information instructing a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band; transmit carrier information instructing the second network node to use one or more downlink carriers and one or more uplink carriers for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; and participate in wireless communication via the first downlink carrier and the first uplink carrier according to the carrier information.

[0036] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information includes a first indication that the second network node supports communication in a first frequency band and a second indication that the second network node supports communication in a second frequency band, and the capability of the second network node to communicate using the pair of carriers can be indicated by the first indication and the second indication.

[0037] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information includes: a first list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of these individual frequency bands; and a second list of frequency band pairs, wherein for each pair, the second network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with the downlink communication via a second pair of components in the corresponding pair, and the first frequency band and the second frequency band may be one of the frequency band pairs included in the second list.

[0038] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information may indicate one or more first sets of features supported by a second network node and one or more second sets of features supported by a second network node, wherein individual sets of the one or more first sets of features may be associated with a corresponding downlink band in a second list of the band pair, individual sets of the one or more second sets of features may be associated with a corresponding uplink band in a second list of the band pair, and the capability information indicates one or more first sets of features and one or more second sets of features separate from a third set of features supported by the second network node and each associated with a corresponding individual band from the first list.

[0039] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the capability information includes a list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of these individual frequency bands, the list including an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list, and the second frequency band may be included in an additional set of uplink frequency bands, the corresponding individual frequency band belonging to that additional uplink frequency band being the first frequency band.

[0040] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information may indicate one or more first sets of features supported by the second network node and each associated with a corresponding individual frequency band from the list, and the capability information may also indicate one or more second sets of features supported by the second network node and each associated with at least one uplink frequency band from a corresponding set of these additional uplink frequency band sets.

[0041] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the first frequency band may be a TDD frequency band, and the second frequency band may be an FDD frequency band or a SUL frequency band.

[0042] In some aspects of the methods, apparatuses and nontransitory computer-readable media described herein, the one or more downlink carriers include SDL carriers, and the first frequency band may be an SDL band that includes the SDL carriers.

[0043] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, transmitting the carrier information may include operations, features, components, or instructions for: transmitting first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier that can be paired with the first uplink carrier; and transmitting second information indicating a second resource for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers.

[0044] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, participating in wireless communication may include operations, features, components, or instructions for: participating in a random access procedure with a second network node using a first candidate uplink carrier from a set of multiple candidate uplink carriers; and receiving uplink transmissions via a second candidate uplink carrier from the set of multiple candidate uplink carriers after the random access procedure and when the second network node is available in a connected mode.

[0045] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, idle mode and connected mode can be communication states of a second network node relative to a first network node, communication during connected mode can be on resources that can be allocated for use by the second network node, and communication during idle mode can be on resources that can be allocated for use by a common network node.

[0046] A method is described. The method may include: receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in a first frequency band; transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0047] A first network node for wireless communication is described. The first wireless node may include at least one communication interface and at least one processor coupled to the communication interface. The first network node may be configured to: receive capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; transmit carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participate in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0048] Another apparatus is described. This apparatus may include: components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in a first frequency band; components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and components for participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0049] A non-transitory computer-readable medium having code stored thereon for wireless communication is described. When executed by a first network node, the code enables the first network node to: receive capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; transmit carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; and participate in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0050] In some aspects of the methods, apparatuses, and nontransitory computer-readable media described herein, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band, and the capability of the first network node to communicate using the pair of carriers can be indicated by the first indication and the second indication.

[0051] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, the second uplink carrier may be an SUL carrier when the second network node is in idle mode, and may be an uplink component carrier for CA when the second network node is in connected mode.

[0052] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, receiving the carrier information may include operations, features, components, or instructions for: transmitting first information indicating a first resource for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier that can be paired with the first uplink carrier; and transmitting second information indicating a second resource for the second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers.

[0053] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, participating in wireless communication may include operations, features, components, or instructions for: participating in a random access procedure with a second network node using a first candidate uplink carrier from a set of multiple candidate uplink carriers; and receiving uplink transmissions via a second candidate uplink carrier from the set of multiple candidate uplink carriers after the random access procedure and when the second network node is available in a connected mode.

[0054] In some aspects of the methods, apparatus, and nontransitory computer-readable media described herein, idle mode and connected mode can be communication states of a second network node relative to a first network node, communication during connected mode can be on resources that can be allocated for use by the second network node, and communication during idle mode can be on resources that can be allocated for use by a common network node.

[0055] In some aspects of the methods, apparatuses and nontransitory computer-readable media described herein, the first frequency band may be a TDD frequency band.

[0056] A method for wireless communication performed by a first network node is described. The method may include: receiving first information indicating first resources for the first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band; receiving second information indicating second resources for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; when the first network node is in an idle mode, determining a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers; and when the first network node is in a connected mode, determining a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers.

[0057] A first network node is described. The first network node may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: receive first information indicating first resources for the first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band; receive second information indicating second resources for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; when the first network node is in an idle mode, determine a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers; and when the first network node is in a connected mode, determine a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers.

[0058] Another first network node is described. This first network node may include: means for receiving first information indicating first resources for the first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band; means for receiving second information indicating second resources for the first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a set of multiple candidate uplink carriers; means for determining a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers when the first network node is in an idle mode; and means for determining a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers when the first network node is in a connected mode.

[0059] A non-transitory computer-readable medium having code stored thereon for wireless communication is described. When executed by a first network node, the code causes the first network node to: receive first information indicating first resources for communication via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band; receive second information indicating second resources for communication via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a set of multiple candidate uplink carriers; when the first network node is in an idle mode, determine a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers; and when the first network node is in a connected mode, determine a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers.

[0060] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, receiving the second information may include operations, features, components, or instructions for receiving a broadcast or private message including the second information, wherein the second information may indicate at least one of the following: frequency information of each of the one or more second uplink carriers, uplink bandwidth portion information of each of the one or more second uplink carriers, or timer information relating to the time alignment of each of the one or more second uplink carriers.

[0061] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, the second information includes criteria for determining a first candidate uplink carrier by the first network node.

[0062] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, determining a first candidate uplink carrier may include operations, features, components, or instructions for: determining a received power value; and determining a first uplink carrier or one of a plurality of second uplink carriers as a first candidate uplink carrier based on a first comparison of the received power value with a first received power threshold.

[0063] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, the standard includes one or more second receive power thresholds and an association between each of one or more second uplink carriers and a corresponding receive power value range, each corresponding receive power value range being defined by at least one of the one or more second receive power thresholds.

[0064] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, determining a first candidate uplink carrier from one or more second uplink carriers may be based on a second comparison of a received power value with one or more second received power thresholds.

[0065] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing a random access procedure using a first candidate uplink carrier and a first downlink carrier, wherein one of one or more second uplink carriers may be the first candidate uplink carrier.

[0066] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, performing a random access procedure may include operations, features, components, or instructions for: transmitting a random access message via a first candidate uplink carrier; monitoring a downlink channel in response to a random access response message transmitted via a first downlink carrier, wherein the random access response message is scheduled for transmission of an uplink shared channel message via the first candidate uplink carrier; transmitting an uplink shared channel message based on the random access response message via the first candidate uplink carrier; and receiving a contention-resolved downlink message based on the uplink shared channel message via the first downlink carrier.

[0067] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, performing a random access procedure may include operations, features, components, or instructions for: transmitting a random access message via a first candidate uplink carrier; and monitoring the downlink channel based on the random access message for downlink messages transmitted via a first downlink carrier.

[0068] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, determining a second candidate uplink carrier may include operations, features, components, or instructions for determining a first uplink carrier as a second candidate uplink carrier, wherein the determination of the first uplink carrier may be based on one of one or more second uplink carriers being determined as the first candidate uplink carrier for a random access procedure.

[0069] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for: transmitting a feedback message via a first uplink carrier in response to the end of a random access procedure; and transmitting the uplink transmission via at least the first uplink carrier.

[0070] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for: transmitting a feedback message via a first candidate uplink carrier in response to the end of a random access procedure; and transmitting the uplink transmission via at least the first candidate uplink carrier.

[0071] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a group of multiple uplink transmissions via at least the first uplink carrier, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on the first downlink carrier may be the same as a second value of a second carrier information field for scheduling uplink transmissions via one uplink of the first uplink carrier in a group of multiple uplink transmissions, and wherein the first value may be different from a third value of a third carrier information field for scheduling uplink transmissions via another uplink of one or more second uplink carriers in a group of multiple uplink transmissions.

[0072] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, determining a second candidate uplink carrier may include operations, features, components, or instructions for determining one of one or more second uplink carriers as a second candidate uplink carrier, wherein the determination of that one of the one or more second uplink carriers may be based on the fact that that one of the one or more second uplink carriers is determined as a first candidate uplink carrier for a random access procedure.

[0073] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a set of multiple uplink transmissions via one of the one or more second uplink carriers, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on a first downlink carrier may differ from a second value of a second carrier information field for scheduling uplink transmissions via one of the one or more second uplink carriers in a set of multiple uplink transmissions, and wherein the first value may differ from a third value of a third carrier information field for scheduling uplink transmissions via another uplink transmission of another of the one or more second uplink carriers in a set of multiple uplink transmissions.

[0074] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for: transmitting a feedback message via one of the one or more second uplink carriers in response to the end of a random access procedure; and transmitting the uplink transmission via at least one of the one or more second uplink carriers.

[0075] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, uplink transmission includes one or more of uplink control channel messages, uplink shared channel messages, or random access channel messages.

[0076] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, the second candidate uplink carrier may be an uplink component carrier for CA when the first network node is in connected mode.

[0077] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, a second candidate uplink carrier may be associated with a corresponding set of feedback procedures.

[0078] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, a combination of one or more second candidate uplink carriers, including the second candidate uplink carrier, may be based on the capabilities of the first network node.

[0079] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for switching from a second candidate uplink carrier to a different second candidate uplink carrier based on the capabilities of the first network node.

[0080] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, a second candidate uplink carrier may be scheduled based on downlink messages associated with the same cell.

[0081] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, half-duplex or full-duplex operation between a first downlink carrier and a second candidate uplink carrier may be based on the capabilities of the first network node.

[0082] In some examples of the methods, apparatuses, first network nodes and nontransitory computer-readable media described herein, the first uplink carrier and one or more second uplink carriers may be in different frequency bands.

[0083] In some examples of the methods, apparatuses, first network nodes and nontransitory computer-readable media described herein, a first uplink carrier and one or more second uplink carriers may be in the same frequency band.

[0084] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, a first uplink carrier and one or more second uplink carriers may be used for communication between the first network node and different cells.

[0085] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, a first uplink carrier and one or more second uplink carriers may be used for communication between the first network node and the same cell.

[0086] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, idle mode and connected mode can be communication states of the first network node relative to a second network node, wherein communication during connected mode can be on resources that can be allocated for use by the first network node, and wherein communication during idle mode can be on resources that can be allocated for use by a common network node.

[0087] In some examples of the methods, apparatus, first network node and nontransitory computer-readable medium described herein, the second candidate uplink carrier may be one of a plurality of second candidate uplink carriers in a plurality of candidate uplink carriers.

[0088] A method for wireless communication performed by a first network node is described. The method may include: transmitting first information indicating first resources for a second network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band; transmitting second information indicating second resources for the second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; participating in a random access procedure with the second network node using a first candidate uplink carrier from the set of multiple candidate uplink carriers; and receiving uplink transmissions via second candidate uplink carriers from the set of multiple candidate uplink carriers after the random access procedure and while the second network node is in connected mode.

[0089] A first network node is described. The first network node may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: transmit first information indicating first resources for a second network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band; transmit second information indicating second resources for the second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; participate in a random access procedure with the second network node using the first candidate uplink carrier from the set of multiple candidate uplink carriers; and receive uplink transmissions via the second candidate uplink carriers from the set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0090] Another first network node is described. This first network node may include: means for transmitting first information indicating first resources for a second network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band; means for transmitting second information indicating second resources for the second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; means for participating in a random access procedure with the second network node using a first candidate uplink carrier from the set of multiple candidate uplink carriers; and means for receiving uplink transmissions via second candidate uplink carriers from the set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0091] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network node, the code causes the first network node to: transmit first information indicating a first resource for a second network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band; transmit second information indicating a second resource for the second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of multiple candidate uplink carriers; participate in a random access procedure with the second network node using the first candidate uplink carrier from the set of multiple candidate uplink carriers; and receive uplink transmissions via the second candidate uplink carriers from the set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0092] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, transmitting the second information may include operations, features, components, or instructions for transmitting a broadcast or private message including the second information, wherein the second information may indicate at least one of the following: frequency information of each of the one or more second uplink carriers, uplink bandwidth portion information of each of the one or more second uplink carriers, or timer information relating to the time alignment of each of the one or more second uplink carriers.

[0093] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, the second information includes criteria for determining a first candidate uplink carrier by the second network node.

[0094] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, the standard includes a first received power threshold, and wherein determining a first uplink carrier or one of a plurality of second uplink carriers as a first candidate uplink carrier may be based on a first comparison of a received power value with the first received power threshold.

[0095] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, the standard includes one or more second receive power thresholds and an association between each of one or more second uplink carriers and a corresponding receive power value range, each corresponding receive power value range being defined by at least one of the one or more second receive power thresholds.

[0096] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, determining a first candidate uplink carrier from one or more second uplink carriers may be based on a second comparison of a received power value with one or more second received power thresholds.

[0097] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, participation in a random access procedure may include operations, features, components, or instructions for participating in a random access procedure using a first candidate uplink carrier and a first downlink carrier, wherein one of one or more second uplink carriers may be the first candidate uplink carrier.

[0098] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, participation in a random access procedure may include operations, features, components, or instructions for: receiving a random access message via a first candidate uplink carrier; transmitting a random access response message via a first downlink carrier, wherein the random access response message is scheduled for transmission of an uplink shared channel message via the first candidate uplink carrier; receiving an uplink shared channel message based on the random access response message via the first candidate uplink carrier; and transmitting a contention-resolving downlink message for a contention-resolving procedure via the first downlink carrier based on the uplink shared channel message.

[0099] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, participation in the random access process may include operations, features, components, or instructions for: receiving a random access message via a first candidate uplink carrier; and transmitting a downlink message via a first downlink carrier based on the random access message.

[0100] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, at least the first uplink carrier may be determined as a second candidate uplink carrier based on one of one or more second uplink carriers being determined as a first candidate uplink carrier for a random access procedure.

[0101] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for: receiving a feedback message via a first uplink carrier in response to the end of a random access procedure; and receiving the uplink transmission via at least the first uplink carrier.

[0102] Some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for: receiving a feedback message via a first candidate uplink carrier in response to the end of a random access procedure; and receiving the uplink transmission via at least the first candidate uplink carrier.

[0103] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a set of multiple uplink transmissions via at least the first uplink carrier, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on the first downlink carrier may be the same as a second value of a second carrier information field for scheduling uplink transmissions via one uplink of the first uplink carrier in a set of multiple uplink transmissions, and wherein the first value may be different from a third value of a third carrier information field for scheduling uplink transmissions via another uplink of one or more second uplink carriers in a set of multiple uplink transmissions.

[0104] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, at least one of the one or more second uplink carriers may be determined as a second candidate uplink carrier based on the determination of one of the first or second uplink carriers as a first candidate uplink carrier for a random access procedure.

[0105] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a set of multiple uplink transmissions via one of the one or more second uplink carriers, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on a first downlink carrier may differ from a second value of a second carrier information field for scheduling uplink transmissions via one of the one or more second uplink carriers in a set of multiple uplink transmissions, and wherein the first value may differ from a third value of a third carrier information field for scheduling uplink transmissions via another uplink transmission of another of the one or more second uplink carriers in a set of multiple uplink transmissions.

[0106] Some examples of the methods, apparatus, first network nodes, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a feedback message via one of the one or more second uplink carriers in response to the end of a random access procedure; and receiving the uplink transmission via at least one of the one or more second uplink carriers.

[0107] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, uplink transmission includes one or more of uplink control channel messages, uplink shared channel messages, or random access channel messages.

[0108] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, the second candidate uplink carrier may be an uplink component carrier for CA when the second network node is in connected mode.

[0109] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, a second candidate uplink carrier may be associated with a corresponding set of feedback procedures.

[0110] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, a combination of one or more second candidate uplink carriers, including the second candidate uplink carrier, may be based on the capabilities of the second network node.

[0111] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, a second candidate uplink carrier may be scheduled based on downlink messages associated with the same cell.

[0112] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, half-duplex or full-duplex operation between a first downlink carrier and a second candidate uplink carrier may be based on the capabilities of the second network node.

[0113] In some examples of the methods, apparatuses, first network nodes and nontransitory computer-readable media described herein, the first uplink carrier and one or more second uplink carriers may be in different frequency bands.

[0114] In some examples of the methods, apparatuses, first network nodes and nontransitory computer-readable media described herein, a first uplink carrier and one or more second uplink carriers may be in the same frequency band.

[0115] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, a first uplink carrier and one or more second uplink carriers may be used for communication between the second network node and different cells.

[0116] In some examples of the methods, apparatuses, first network nodes, and nontransitory computer-readable media described herein, a first uplink carrier and one or more second uplink carriers may be used for communication between the second network node and the same cell.

[0117] In some examples of the methods, apparatus, first network node, and nontransitory computer-readable medium described herein, idle mode and connected mode can be communication states of the first network node relative to a second network node, wherein communication during connected mode can be on resources that can be allocated for use by the second network node, and wherein communication during idle mode can be on resources that can be allocated for use by a common network node. Attached Figure Description

[0118] Figure 1 Examples of wireless communication systems are shown that support capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also support a framework for supplementary uplink (SUL) and uplink carrier aggregation (CA).

[0119] Figure 2 Examples of wireless communication systems are shown that support signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also support frameworks for SUL and uplink CA, according to one or more aspects of this disclosure.

[0120] Figure 3Examples of random access procedures for the framework of SUL and uplink CA are shown, according to one or more aspects of this disclosure, supporting capability signaling for downlink and uplink carriers and cells in different frequency bands and also supporting the framework for uplink CA.

[0121] Figure 4 and Figure 5 An example of a communication framework is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports the framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0122] Figure 6 Examples of carrier configurations for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, are shown.

[0123] Figure 7 and Figure 8 Examples of process flows that support capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also support frameworks for SUL and uplink CA, are shown.

[0124] Figure 9 and Figure 10 A block diagram of an apparatus is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0125] Figure 11 A block diagram of a communication manager is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0126] Figure 12 A block diagram of an apparatus is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0127] Figure 13 A block diagram of a communication manager is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0128] Figure 14A diagram is shown of a system comprising a device according to one or more aspects of this disclosure, including capability signaling for downlink and uplink carriers and cells in different frequency bands, and also supporting a framework for SUL and uplink CA.

[0129] Figure 15 and Figure 16 A block diagram of an apparatus is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0130] Figure 17 A block diagram of a communication manager is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0131] Figure 18 A block diagram of an apparatus is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0132] Figure 19 A block diagram of a communication manager is shown that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework for SUL and uplink CA, according to one or more aspects of this disclosure.

[0133] Figure 20 A diagram is shown of a system comprising a device according to one or more aspects of this disclosure, including capability signaling for downlink and uplink carriers and cells in different frequency bands, and also supporting a framework for SUL and uplink CA.

[0134] Figures 21 to 31 A flowchart illustrating a method for supporting capability signaling for downlink and uplink carriers and cells in different frequency bands, and also supporting a framework for SUL and uplink CA, is shown. Detailed Implementation

[0135] User equipment (UE) can support uplink and downlink carrier pairs for communication with the cell, where both the uplink and downlink carriers can be in the same frequency range. In some cases, the UE can support additional uplink carriers, such as supplementary uplink (SUL) carriers or uplink component carriers (which can be used for carrier aggregation (CA)). When the additional uplink carrier is an SUL carrier, the UE can be configured with two uplink carriers and one downlink carrier for the same cell. The SUL carrier can support both idle mode and connected mode operation in the UE. When in connected mode (e.g., when communicating with a network entity), the UE can transmit uplink messages at any given time on the paired uplink carrier (e.g., the normal uplink carrier) or on the SUL carrier.

[0136] Furthermore, the UE can monitor downlink messages on one cell, which schedule uplink messages on different cells (e.g., Physical Uplink Shared Channel (PUSCH) transmissions). This cross-carrier scheduling is available to the UE when CA is supported. SUL carriers and CA are different mechanisms that enable the UE to perform many of the same functions. However, SUL carriers and CA are configured differently and subject to different limitations. For example, SUL carriers can support both idle and connected modes of the UE, while uplink CA may only support connected mode. Additionally, SUL carrier communication may lack support for simultaneous transmission, while uplink CA allows simultaneous transmission.

[0137] In some cases, the UE may support communication using uplink-downlink carrier pairs, and in others, communication using SUL carriers across different frequency bands or combinations of frequency bands. The UE may report a list of frequency bands it supports and a list of frequency band combinations that can be configured to have a CA with a network entity. For example, the UE may support communication using uplink and downlink carriers within a single cell in band n79 or band n3. However, the UE may lack a method for reporting its ability to communicate using uplink and downlink carriers in different frequency bands (e.g., a downlink carrier in band n79 and an uplink carrier in band n3). Additionally, the UE may currently lack the ability to communicate in the Supplemental Downlink (SDL) band and with uplink and SUL carriers in different frequency bands.

[0138] The techniques described herein support capability signaling for downlink and uplink carriers and cells in different frequency bands. For example, a UE can report UE capabilities that support communication using downlink and uplink (including SUL or enhanced SUL (eSUL)) carriers in different frequency bands. In some aspects, a UE can indicate the capability to communicate using uplink-downlink carrier pairs, where these uplink and downlink carriers are used in different frequency bands. The UE can receive carrier information based on this capability, indicating one or more uplink and downlink carriers that the UE intends to use for wireless communication. The UE can then use the indicated uplink and downlink carriers to participate in wireless communication.

[0139] Alternatively, the UE may indicate the capability to communicate using uplink-downlink carrier pairs in the same frequency band. In such cases, the UE may receive carrier information indicating one or more uplink and downlink carriers for which the UE intends to use wireless communication, wherein the one or more uplink carriers include a normal uplink carrier (e.g., an uplink carrier in an uplink-downlink carrier pair) and an eSUL carrier. Furthermore, the carrier information may include second carrier information based on the capability and based on the fact that the normal uplink carrier and the eSUL carrier are in the same frequency band. The UE may use the downlink carrier and the eSUL carrier to participate in wireless communication.

[0140] Furthermore, the techniques described herein support a unified framework for SUL carriers and uplink CAs in wireless communication systems. Network entities can send broadcast or dedicated messages to the UE indicative (configured to the UE) of the cell's uplink and downlink carrier pairs and one or more additional uplink carriers (which may be referred to as eSUL carriers). The UE can use the additional uplink carriers as SUL carriers when the UE is in idle mode, or as component carriers of the CA when the UE is in connected mode. For example, when the UE determines the cell to access (when in idle mode), the UE can select or determine a candidate carrier (either a normal uplink carrier or one of the additional uplink carriers) for performing a random access procedure. For example, if the UE selects one of the additional uplink carriers, the UE can use that additional uplink carrier as an SUL carrier to perform a 2-step or 4-step random access procedure. Based on successful contention resolution, the UE can enter connected mode and use one or more of the normal uplink carriers or additional uplink carriers (as component carriers in the CA) to perform subsequent uplink transmissions. The UE can perform uplink transmissions using an additional uplink carrier or a normal uplink carrier, based on the carrier used for the random access procedure.

[0141] The aspects of this disclosure are first described in the context of a wireless communication system. Then, the aspects of this disclosure are described in the context of a random access procedure, a communication framework, and a process flow. Further, the aspects of this disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to capability signaling for downlink and uplink carriers and cells in different frequency bands.

[0142] Figure 1 An example of a wireless communication system 100 is shown that supports capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework (e.g., an eSUL framework) for SUL and uplink CA. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some aspects, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0143] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some aspects, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support a coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support signal transmission according to one or more radio access technologies (RATs).

[0144] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein can be able to support communication with various types of devices, such as other UE 115s or network entities 105, such as Figure 1 As shown.

[0145] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of (e.g., as a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. In another example, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet another aspect of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, or a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0146] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a first network node being configured to provide, transmit, output, communicate, or send information to a second network node. Similarly, in this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a second network node being configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0147] In some aspects, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some aspects, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some aspects, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0148] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some aspects, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, self-contained) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0149] In some aspects, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize a protocol stack physically or logically distributed among two or more network entities 105 (such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN))). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. RU 170 may also be referred to as a radio headend, an intelligent radio headend, a remote radio headend (RRH), a remote radio unit (RRU), or a transmit-receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some aspects, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0150] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some respects, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, protocol stack functional splitting can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some respects, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, each layer of which is supported by the corresponding network entity 105 communicating via such communication links.

[0151] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some aspects, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0152] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 can communicate with the core network via an interface (which may be part of a backhaul link) and can communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0153] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115.

[0154] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0155] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support capability signaling for downlink and uplink carriers and cells in different frequency bands as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0156] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some aspects, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, which can be implemented in various objects such as electrical appliances or vehicles, instruments, etc.

[0157] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown.

[0158] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using CA or multi-carrier operation. UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers according to CA configuration. CA can be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0159] In some aspects, such as in a CA configuration, the carrier may also have acquisition signaling or control signaling to coordinate operation for other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. The carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via the carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0160] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0161] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some aspects, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some aspects, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some aspects, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0162] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high amount of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0163] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( The carrier can be divided into one or more BWPs with the same or different sets of parameters. In some respects, the UE 115 can be configured with multiple BWPs. In some respects, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be limited to one or more active BWPs.

[0164] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0165] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some aspects, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include variable time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0166] A subframe, time slot, micro-time slot, or symbol may be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and may be referred to as a transmission time interval (TTI). In some respects, the duration of the TTI (e.g., the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0167] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of the physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set configured to transmit control information to a specific UE 115.

[0168] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some aspects, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110.

[0169] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0170] In some respects, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0171] In some aspects, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some aspects, while different coverage areas 110 associated with different technologies may overlap, different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0172] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some aspects, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0173] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0174] In some aspects, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some aspects, one or more UEs 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by network entity 105. In some aspects, one or more UEs 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some aspects, the group of UEs 115s communicating via D2D communication may support a one-to-many (1:M) system, wherein each UE 115 transmits to every other UE 115 in the group. In some respects, network entity 105 can facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0175] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through user plane entities, which provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0176] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave communication can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0177] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some aspects, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands based on CA configuration (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0178] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some aspects, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0179] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include the transmitting or receiving device applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0180] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0181] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some aspects, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to a different time interval.

[0182] In the wireless communication system 100, the UE 115 can support uplink and downlink carrier pairs of the serving cell in the wireless communication system 100. Furthermore, the UE 115 can support SUL carriers, which can be additional uplink carriers associated with the serving cell. Therefore, using SUL carriers, the UE 115 can be configured with two uplink carriers and one downlink carrier for the same cell. The SUL carriers can be configured to improve uplink coverage in high-frequency scenarios. Additionally, the UE 115 can support two methods for operating multiple uplink carriers. For example, the UE 115 can support SUL, which can be an uplink carrier or frequency band that supplements the uplink coverage of the serving cell. Alternatively, the UE 115 can support uplink CA, which may include multiple uplink component carriers that the UE 115 can use to transmit simultaneously or switch transmissions.

[0183] The SUL carrier can support both idle mode (e.g., RRC_IDLE) and connected mode (e.g., RRC_CONNECTED). For example, when in idle mode, UE 115 can receive broadcast messages such as System Information Blocks (SIBs) (e.g., SIB1) or dedicated messages, and identify the SUL configuration from information in that SIB1 (e.g., supplementaryUplink in ServingCellConfigCommonSIB). For example, ServingCellConfigCommonSIB may include both UplinkConfigCommon and supplementaryUplink information elements. The UE can trigger a random access procedure to enter connected mode on either the cell's normal uplink carrier or the SUL. The carrier on which UE 115 transmits Physical Random Access Channel (PRACH) messages can be based on several standards. For example, if the serving cell used for the random access procedure is configured with a SUL, and if the reference received signal power (RSRP) for downlink path loss reference is less than a threshold (e.g., rsrp-ThresholdSSB-SUL), then UE 115 may select the SUL carrier to perform the random access procedure and set the maximum transmit power PCMAX to the P of the SUL carrier. CMAX,f,c If RSRP is greater than the threshold, UE 115 may select a normal uplink carrier (from the uplink and downlink carrier pair) to perform the random access procedure, setting the maximum transmit power PCMAX to the P of the normal uplink carrier. CMAX,f,c .

[0184] When operating in connected mode, UE 115 can be configured to transmit uplink messages at any given time using either a normal uplink carrier or a SUL carrier (e.g., not simultaneously on both carrier types), or to receive instructions to transmit uplink messages at any given time using either of the aforementioned carriers. For example, network entity 105 can be semi-statically configured to transmit the Physical Uplink Control Channel (PUCCH) on either a normal uplink carrier or a SUL carrier.

[0185] Network entity 105 can be semi-statically configured or dynamically indicated for PUSCH transmissions to be transmitted by UE 115 on a normal uplink carrier or a SUL carrier. If UE 115 supports dynamic scheduling of PUSCH transmissions on a normal uplink carrier or a SUL carrier of the serving cell, and if network entity 105 configures a normal uplink carrier or a SUL carrier of the serving cell, the downlink control information (DCI) format for PUSCH scheduling may include a one-bit uplink / SUL indicator that indicates the carrier on which the DCI is scheduling PUSCH transmissions. If network entity 105 configures PUSCH transmissions on only one of the uplink carriers or SUL carriers, the PUSCH transmissions are scheduled on the carrier on which the PUSCH transmissions are configured. If network entity 105 does not configure PUSCH transmissions on either the uplink carrier or the SUL carrier, the PUSCH transmissions are scheduled on the carrier on which the PUCCH transmissions are configured. Alternatively, if network entity 105 is not configured to transmit PUSCH on either the uplink carrier or the SUL carrier, and if network entity 105 is not configured to transmit PUCCH, then network entity 105 may schedule PUSCH transmission on the carrier on which the latest PRACH message has been transmitted.

[0186] Additionally or alternatively, network entity 105 may be semi-statically configured or dynamically indicated to transmit PRACH on a normal uplink carrier or a SUL carrier, or UE 115 may choose to transmit PRACH on either a normal uplink carrier or a SUL carrier. If network entity 105 is configured to transmit PRACH on only a normal uplink carrier or a SUL carrier, the configured carrier can be used to perform PRACH transmission. Alternatively, if network entity 105 is configured to transmit PRACH on both a normal uplink carrier and a SUL carrier, UE 115 may select the normal uplink carrier or SUL carrier for PRACH transmission based on the RSRP of the downlink path loss reference signal (e.g., the synchronization signal block (SSB) - RSRP). For PRACH transmission ordered by the physical downlink control channel (PDCCH), the corresponding DCI format may include a one-bit uplink / SUL indicator indicating the carrier on which the DCI format can trigger PRACH transmission.

[0187] In some cases, UE 115 can be configured to monitor the PDCCH on one cell to obtain PUSCH scheduling on another cell. This PDCCH may correspond to DCI format 0_1 ​​or 0_2, including a Carrier Indicator Field (CIF), where the CIF value indicates the cell to which the DCI sends its scheduled PUSCH. In such cases, DCI format 0_0 may lack support for cross-carrier scheduling. More specifically, UE 115 can be configured to monitor a search space set to obtain the PDCCH on one cell for PUSCH scheduling on another cell, and in this case, network entity 105 may send (and UE 115 may detect) the PDCCH in DCI format 0_1 ​​or 0_2 (but not DCI format 0_0) for PUSCH scheduling on the other cell. On the scheduled cell, UE 115 can monitor the PDCCH individually for different scheduled cells. The set of Control Channel Elements (CCEs) for PDCCH candidates for each scheduled cell can be derived based on different parameters (e.g., n_Cl values). Therefore, the CCE sets are typically different. Furthermore, the DCI format size can be different for different scheduled cells, and the number of blind decoding (BD) and CCE for PDCCH candidates can be counted differently for different scheduled cells. Additionally, HARQ space can be prepared separately for different scheduled cells.

[0188] In some aspects, the wireless communication system 100 may support multi-carrier scheduling. The UE 115 may be configured to monitor a PDCCH on a single cell for scheduling PUSCHs on more than one cell. In this case, each PUSCH on each corresponding cell may be scheduled. The DCI format for multi-cell PUSCH scheduling (e.g., DCI format 0_3) may include a “set-CIF” field, where the value of the “set-CIF” field indicates the set of cells that can be scheduled by the DCI. Different “set-CIF” field values ​​may be configured for different cell sets. Furthermore, within the cell set indicated by the “set-CIF” field, all or a subset of these cells may be scheduled by each DCI. More specifically, the UE 115 may be configured with a mapping between the value of the “set-CIF” field of DCI format 0_3 and the cell set used for multi-cell PUSCH scheduling. If the UE 115 detects a DCI format 0_3 with a “set-CIF” field value associated with a cell set, then DCI format 0_3 may schedule one or more or all cells in that cell set. UE 115 can identify one or more cells that are actually scheduled by DCI format 0_3 by indicating another specific field of the subset of cells actually scheduled by DCI format 0_3, or based on whether the Frequency Domain Resource Allocation (FDRA) field for each cell in DCI format 0_3 is set to "No RBs are scheduled".

[0189] However, the SUL carrier and uplink CA are configured separately and subject to different constraints, and therefore can support different communications. For example, regarding the band combination framework, the SUL carrier can support SUL-specific bands, where the combination of normal and SUL bands can be defined as needed. For uplink CA, normal bands can be aggregated under the CA band combination framework. Furthermore, the SUL carrier can support both idle and connected modes of UE 115, while the uplink CA can only support connected mode. Additionally, SUL may lack support for simultaneous transmission, while uplink CA can support simultaneous transmission. Moreover, SUL and CA can utilize different carrier indications. For example, the uplink / SUL indicator in the DCI can indicate the uplink carrier from the cell for both the normal uplink carrier and the SUL carrier, and the CIF in the DCI can be used for CA. Although SUL may not support multi-cell scheduling, the carrier used for multi-cell scheduling can be indicated via the Co-Scheduled Cell Indication field or the FDRA field of the CA. Furthermore, uplink transmission handover may be a SUL-specific behavior for SUL, and for CA it may be supported by both "switchedUL" and "dualUL". Therefore, SUL and uplink CA are based on different mechanisms, and thus require specifically defined implementations and UE capabilities. Therefore, a unified framework for SUL and uplink CA is needed.

[0190] Wireless communication system 100 supports technology for capability signaling for downlink and uplink carriers and cells in different frequency bands or within the same frequency band. In some aspects, UE 115 may indicate the capability to communicate using uplink-downlink carrier pairs, wherein the uplink and downlink carriers are used in different frequency bands or within the same frequency band. UE 115 may receive carrier information based on this capability, indicating one or more uplink and downlink carriers for which UE 115 intends to use wireless communication. In some aspects, the uplink carriers indicated in the carrier information may include normal uplink carriers and cells, as well as SUL (e.g., eSUL) carriers and cells. Where UE 115 is capable of communicating using uplink-downlink carrier pairs within the same frequency band, the carrier information may include second carrier information based on this capability and based on the fact that the normal uplink carrier and eSUL carrier are in the same frequency band. UE 115 may participate in wireless communication using indicated downlink and uplink carriers in the same or different frequency bands, or indicated downlink and eSUL carriers in the same or different frequency bands.

[0191] Furthermore, the wireless communication system 100 supports technologies for implementing a unified framework for SUL and uplink CA. Network entity 105 can send a broadcast or dedicated message to UE 115 instructing (configured to UE 115) the uplink and downlink carrier pairs of a cell and one or more additional uplink carriers, which can be an additional SUL or an enhanced SUL (eSUL) carrier (e.g., a second uplink carrier) or an enhanced SUL cell. An eSUL carrier is an additional SUL carrier that UE 115 can use as an eSUL in idle mode or as a CC in CA in connected mode. For example, when UE 115 determines to access a cell (in idle mode), UE 115 can select or determine a candidate carrier (normal uplink carrier or eSUL carrier) for performing a random access procedure. For the uplink carrier selected by UE 115, UE 115 can use that carrier to perform a 2-step or 4-step random access procedure. Based on successful contention resolution, UE 115 can enter connected mode and perform subsequent uplink transmissions using either a normal uplink carrier or an eSUL carrier, which has been determined as the second candidate uplink carrier. UE 115 can perform uplink transmissions using either a normal uplink carrier or an eSUL carrier based on the carrier used for the random access procedure.

[0192] Figure 2An example of a wireless communication system 200 is shown that supports capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework (e.g., an eSUL framework) for SUL and uplink CA. In some aspects, the wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented through aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network nodes 205-a and 205-b, which may be examples of UE 115 and network entity 105 described herein, respectively. Network nodes 205-a and 205-b may support uplink and downlink carriers.

[0193] Wireless communication system 200 can support communication between network node 205-a and network node 205-b via communication link 210, which can be referred to herein. Figure 1 An example of the described communication link 125. For example, network nodes 205-a and 205-b can perform uplink and downlink communication via communication link 210. In some aspects, network node 205-a can operate in different communication states, including idle mode or connected mode. Communication during idle mode can occur on resources allocated for use by common network nodes. That is, during idle mode, network node 205-a can periodically become available to monitor the downlink channel without being connected to a specific network entity 105. Communication during connected mode can occur on resources allocated for use by network node 205-a. That is, network node 205-a can wirelessly connect to network node 205-b when in connected mode.

[0194] In some respects, network node 205-b may configure uplink and downlink carrier pairs to network node 205-a. For example, network node 205-a may receive message 215 (e.g., a broadcast message such as SIB1, or a higher-level dedicated message) associated with a cell and indicating that network node 205-a may use a first resource for communication via at least one of downlink carrier 220 and uplink carrier 225 defined in the same or different frequency bands. Downlink carrier 220 may correspond to an FDD cell, carrier, or frequency band, a TDD cell, carrier, or frequency band, or a supplemental downlink (SDL) cell, carrier, or frequency band.

[0195] Additionally, network node 205-b can configure one or more additional uplink carriers associated with the cell to network node 205-a. These additional uplink carriers may be additional uplink carriers 230 that lack a corresponding downlink carrier. The additional uplink carrier 230 may be an SUL carrier in an SUL band, an uplink carrier in an FDD cell, carrier, or band, or an uplink resource in a TDD cell, carrier, or band. Furthermore, network node 205-a may use one uplink carrier from uplink carrier 225 and additional uplink carrier 230 when operating in idle mode, or one or more of uplink carrier 225 and additional uplink carrier 230 when operating in connected mode. When UE 115 operates in connected mode, each or more of uplink carrier 225 and additional uplink carrier 230 are considered regular uplink component carriers in the uplink CA.

[0196] In some aspects, message 215 may additionally indicate a second resource for network node 205-a to use for communication via an additional uplink carrier 230 (also referred to herein as a second uplink carrier or eSUL) associated with downlink carrier 220 but different from uplink carrier 225. For example, the additional uplink carrier 230 may include additional uplink carrier 230-a, additional uplink carrier 230-b, or any other number of additional uplink carriers 230 supported by wireless communication system 200. Each additional uplink carrier 230 may be an eSUL. Commonly, uplink carrier 225 and additional uplink carrier 230 may be a group of multiple candidate uplink carriers. In some cases, uplink carrier 225 and additional uplink carrier 230 may be in the same frequency band or different frequency bands. Additionally, uplink carrier 225 and additional uplink carrier 230 may be used for communication between network node 205-a and the same or different cells. In some respects, information associated with the additional uplink carrier 230 may be indicated in message 215 via UplinkConfigCommonSIB or equivalent information. Message 215 may include frequency information, uplink BWP information (e.g., uplink BWP common configuration), or timer information (e.g., time alignment timer configuration) related to time alignment associated with each of the additional uplink carriers 230.

[0197] When operating in idle mode, network node 205-a can determine or select a first candidate uplink carrier from a set of multiple candidate uplink carriers for the random access procedure. That is, when network node 205-a determines to access a cell, it can select one of the cell's uplink carrier 225 or an additional uplink carrier 230 for the random access procedure. In some aspects, message 215 may include criteria for determining the first candidate uplink carrier. For example, message 215 may indicate one or more RSRP thresholds and a mapping (provided by parameters or a parameter list) between an RSRP range and one of the uplink carrier 225 or the additional uplink carrier 230, where the RSRP range includes RSRP values ​​between (or is defined by) two RSRP thresholds. Network node 205-b can provide a list of RSRP thresholds for the cell's SSB (or Channel State Information (CSI)-Reference Signal (CSI-RS) or any other downlink reference signal that can be used to measure the downlink RSRP), as well as uplink or SUL carrier indices mapped to each RSRP range.

[0198] When the standard indicates one or more RSRP thresholds, network node 205-a can determine the cell's RSRP (or other received power value) and, based on comparing the measured RSRP with one or more RSRP thresholds indicated in message 215, determine a first candidate uplink carrier as either uplink carrier 225 or an additional uplink carrier 230. For example, if the cell's RSRP is below a first threshold (e.g., threshold 1), network node 205-a can select uplink carrier 225. If the cell's RSRP is between the first and second thresholds (e.g., threshold 2), network node 205-a can select additional uplink carrier 230-a (e.g., eSUL carrier #1). If the cell's RSRP is between the second and third thresholds (e.g., threshold 3), network node 205-a can select additional uplink carrier 230-b (e.g., eSUL carrier #2). If the RSRP of the cell is greater than the third threshold, network node 205-a may select a third additional uplink carrier 230 (e.g., eSUL carrier #3).

[0199] In some respects, network node 205-a may independently (e.g., based on its own decision) select one of the uplink carriers 225 or 230 as the first candidate uplink carrier for the random access procedure. Alternatively, network node 205-a may determine the first candidate uplink carrier using the criteria indicated in message 215 and its own RSRP measurement. For example, network node 205-a may use one or more RSRP thresholds indicated in message 215 and the determined cell RSRP value to select uplink carrier 225 or 230. If network node 205-a selects 230, it may independently determine which of the 230 additional uplink carriers will be used for the random access procedure (e.g., additional uplink carrier 230-a, additional uplink carrier 230-b, etc.).

[0200] Network node 205-a can use the determined first candidate uplink carrier and downlink carrier 220 to perform a random access procedure. (This document references...) Figure 3 The random access procedure is described. After successful contention resolution, network node 205-a can enter connected mode and, while in connected mode, determine a second candidate uplink carrier from a set of multiple uplink carriers for subsequent uplink transmission 235. That is, once wirelessly connected to network node 205-b, network node 205-a can determine whether to use uplink carrier 225 or an additional uplink carrier 230 to transmit uplink 235. (References) Figure 4 The determination of a second candidate uplink carrier is described. Based on the determination of the second candidate uplink carrier, network node 205-a can use the selected second candidate uplink carrier to send one or more uplink transmissions 235 to network node 205-b.

[0201] In some aspects, network node 205-a may support communication using downlink carrier 220 and uplink carrier 225 or an additional uplink carrier 230 (e.g., eSUL) in different frequency bands, and network node 205-a may indicate the capability to support such communication. In some aspects, network node 205-a may send capability information 240 indicating the capability of network node 205-a to communicate using a pair of carriers (e.g., downlink carrier 220 and uplink carrier 225 or eSUL) in different frequency bands. For example, network node 205-a may indicate support for a first frequency band (e.g., NR band X) and a second frequency band (e.g., NR band Y), and support for communication using downlink carrier 220 in the first frequency band and uplink carrier 225 or an additional uplink carrier 230 in the second frequency band (or using downlink carrier 220 in the second frequency band and uplink carrier 225 or an additional uplink carrier 230 in the first frequency band). In some respects, the first frequency band can be a TDD band, and the second frequency band can be an FDD band or a SUL band, as referenced in this article. Figure 6 As described. Alternatively, the downlink carrier 220 may be an SDL carrier, and the first frequency band may be an SDL band that includes the SDL carrier. The first and second frequency bands may be in frequency ranges (FR) 1, FR2, FR2-1, FR2-2, or FR3.

[0202] In some respects, the capability of network node 205-a can be assumed based on a first indication that network node 205-a supports communication using downlink carrier 220 in the first frequency band (or second frequency band) and a second indication that network node 205-a supports communication using uplink carrier 225 or additional uplink carrier 230 in the second frequency band (or first frequency band).

[0203] In addition to reporting a list of frequency bands supported by network node 205-a (e.g., supportedBandListNR) in capability information 240, network node 205-a may also report a list of its supported downlink and uplink (e.g., {DL,UL}) frequency band pairs. In this way, capability information 240 may include a first list of individual frequency bands, wherein network node 205-a supports both downlink and uplink communication via each of these individual frequency bands. Furthermore, capability information 240 may include a second list of frequency band pairs, wherein network node 205-a supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with that downlink communication via a second pair of components in the corresponding pair. The first and second frequency bands may be one of the frequency band pairs included in the second list.

[0204] In some respects, network node 205-a may also indicate support for optional features for downlink communication using downlink carriers in a given band pair and optional features for uplink communication using uplink or eSUL carriers in a given band pair. That is, capability information 240 may indicate one or more sets of features supported by network node 205-a, these sets of features being associated with the corresponding uplink or downlink band of the band pair.

[0205] In some implementations, capability information 240 may indicate a frequency band sequence (e.g., Band NR), and for each frequency band, a list of optional features supported by network node 205-a, and other corresponding information (additional capabilities, identifiers, etc.), which may be indicated as information elements. For example, these features may include an NR frequency band index, per-band MIMO capability, per-band optional capabilities (e.g., pdsch-256QAM-FR2, pusch-256QAM, rateMatchingLTE-CRS, etc.), the power class of network node 205-a (e.g., ue-PowerClass), the supported subcarrier spacing and channel bandwidth for uplink and downlink (e.g., channelBWs-DL, channelBWs-UL), or any combination thereof. Furthermore, capability information 240 may indicate NR band pair capabilities for communication using downlink and uplink carriers and cells in different frequency bands. For example, in addition to the features described herein and for each frequency band, capability information 240 may indicate an NR band index for downlink communication, which may include downlink-related per-band parameters (features described herein), supported subcarrier spacing and channel bandwidth for the downlink (e.g., channelBWs-DL), per-band optional capabilities for downlink communication (e.g., pdsch-256QAM-FR2), and other features. Furthermore, capability information 240 may indicate an NR band index for uplink communication, which may include uplink-related per-band parameters (features described herein), supported subcarrier spacing and channel bandwidth for the uplink (e.g., channelBWs-UL), per-band optional capabilities for downlink communication (e.g., pdsch-256QAM-FR2), the power class of network node 205-a (e.g., ue-PowerClass), and other features.

[0206] Additionally or alternatively, for each frequency band indicated in the capability information 240 (e.g., Band NR), network node 205-a may include one or more frequency bands that can be associated with the downlink carrier 220 in that frequency band. That is, the capability information 240 may include: a list of individual frequency bands, wherein network node 205-a supports both downlink and uplink communication via each of these individual frequency bands; and an additional set of uplink frequency bands associated with each of these individual frequency bands, which are associated with the eSUL carrier. Furthermore, network node 205-a may (in the capability information 240) indicate support for optional features for downlink communication via the downlink carrier 220 of a given frequency band pair and optional features for uplink communication via the uplink carrier 225 or additional uplink carrier 230 of a given frequency band pair. That is, the capability information 240 may indicate a set of features for individual frequency bands and additional sets of uplink frequency bands.

[0207] In some respects, capability information 240 may indicate a list of optional features supported by network node 205-a for each frequency band, along with other corresponding information (additional capabilities, identifiers, etc.), which may be indicated as information elements as described herein. Furthermore, capability information 240 may indicate a list of frequency bands supported by network node 205-a for eSUL carriers, and a list of optional features for each frequency band, including NR band indexes, uplink-related per-band parameters, supported uplink subcarrier spacing and channel bandwidth (e.g., channelBWs-UL), and the power class of network node 205-a (e.g., ue-PowerClass), as well as other parameters or features. In this way, capability information 240 can instruct network node 205-a to support a first frequency band for downlink communication via downlink carrier 220 and one or more second frequency bands (eSUL bands) for uplink communication via eSUL carrier (with an additional uplink carrier 230), wherein the first frequency band and the second frequency band are associated in capability information 240.

[0208] In response to capability information 240, network node 205-a may receive carrier information 245 indicating one or more downlink carriers and one or more uplink carriers for wireless communication. For example, the one or more downlink carriers may include downlink carrier 220, and the one or more uplink carriers may include uplink carrier 225 or an additional uplink carrier 230 (e.g., eSUL), wherein downlink carrier 220 is associated with the first frequency band, and uplink carrier 225 or the additional uplink carrier 230 is associated with the second frequency band. In some cases, network node 205-a may receive first information and second information indicating first and second resources for communication via downlink and uplink carrier pairs, respectively. Network node 205-a may participate in wireless communication via the indicated downlink and uplink carriers according to carrier information 245.

[0209] In some cases, network node 205-a may support multiple uplink carriers (e.g., uplink carrier 225 and one or more eSUL carriers) associated with downlink carrier 220 in the same frequency band. In such cases, network node 205-a may indicate per-band capabilities of one or more frequency bands (e.g., Band NR) in capability information 240 as described herein. For example, capability information 240 may indicate the ability of network node 205-a to communicate using uplink and downlink carrier pairs in the same frequency band. In some aspects, network node 205-a may support communication using downlink carrier 220 and uplink carrier 225 associated with downlink carrier 220 in the same cell (e.g., configured via RRC information elements uplinkConfigCommon or uplinkConfig). Furthermore, network node 205-a may support communication using downlink carrier 220 and one or more eSUL carriers associated with downlink carrier 220 in the same cell (e.g., configured via RRC information elements eSUL-Config or eSUL-Config lists). In other words, network node 205-a can support the use of the first frequency band (for the same frequency band for uplink and downlink communication, refer to...). Figure 6 The downlink and uplink carrier pairs in the described frequency band 605-a) and the use of a second frequency band different from the first frequency band (e.g., reference 605-a) Figure 6 Communication of the eSUL carrier in the described frequency band 605-b).

[0210] In cases where network node 205-a supports communication using downlink carrier 220 and uplink carriers in the same frequency band, network node 205-a may receive carrier information 245 in response to capability information 240. Carrier information 245 may indicate one or more downlink carriers (e.g., downlink carrier 220) and one or more uplink carriers (e.g., uplink carrier 225, eSUL) for wireless communication by network node 205-a. Furthermore, carrier information 245 may include second carrier information based on capability information 240 and based on the fact that the downlink and uplink carriers are in the same frequency band. Network node 205-a may participate in wireless communication via the indicated downlink and uplink carriers (eSUL) according to carrier information 245.

[0211] Figure 3 Examples of random access procedures 300 and 301, according to one or more aspects of this disclosure, are shown, supporting capability signaling for downlink and uplink carriers and cells in different frequency bands and also supporting frameworks for SUL and uplink CA (e.g., eSUL frameworks). In some aspects, random access procedures 300 and 301 may be implemented by or by aspects of wireless communication systems 100 and 200. For example, network node 205 (e.g., UE 115, network entity 105) may use uplink carrier 310 or additional uplink carrier 315 and downlink carrier 305 to perform random access procedure 300 or random access procedure 301.

[0212] As referenced in this article Figure 2 As described, a network node (e.g., a UE) may use a first candidate uplink carrier and a downlink carrier 305 to perform a random access procedure. The first candidate uplink carrier is determined to be either uplink carrier 310 or an additional uplink carrier 315. The additional uplink carrier 315 may include an eSUL carrier, an SUL carrier in an SUL band, an uplink carrier in an FDD cell, carrier, or band, or uplink resources in a TDD cell, carrier, or band. If the network node selects uplink carrier 310, the network node may use uplink carrier 310 and the paired downlink carrier 305 to perform a random access procedure. If the network node selects additional uplink carrier 315 (e.g., eSUL), the network node may perform a random access procedure based on the additional uplink carrier 315 and the downlink carrier 305 of the associated cell.

[0213] The random access procedure 300 can be an example of a four-step random access procedure based on an additional uplink carrier 315-a. A network node can be configured with a downlink carrier 305-a and an uplink carrier 310-a (which can be a pair of uplink and downlink carriers for the cell) and one or more additional uplink carriers 315 (including the additional uplink carrier 315-a). After determining the additional uplink carrier 315-a as a candidate uplink carrier for the random access procedure 300, the network node can send a random access message (PRACH 320) via the additional uplink carrier 315-a (the first candidate uplink carrier). The network node can monitor the downlink channel (e.g., PDCCH) in response to a random access response (RAR) message 325 sent via the downlink carrier 305-a (e.g., by a network entity). In some respects, PDCCH monitoring can target a type 1 common search space set on the associated cell to obtain DCI format 1_0 with cyclic redundancy check (CRC) scrambled by random access radio network temporary identifier (RA-RNTI). The PDCCH monitoring for the additional uplink carrier 315-a can be a similar process to that for the uplink carrier 310-a.

[0214] In some respects, RAR message 325 can be scheduled to be transmitted via Msg3 330 (e.g., PUSCH) with an additional uplink carrier 315-a (on which the network node has already transmitted PRACH 320). In some respects, retransmission of Msg3 330 PUSCH can be scheduled via DCI with DCI format 0_0 monitored on a type 1 common search space set on the associated cell, which has a CRC scrambled by Temporary Cell (TC)-RNTI.

[0215] A network node may transmit Msg3 330 via an additional uplink carrier 315-a based on RAR message 325. In some cases, a network node may receive Msg4 335 via a downlink carrier 305-a based on Msg3 330, which may be a contention-resolved downlink message. Based on contention resolution, the network node may enter a connection mode with a second network node (e.g., a network entity) and transmit subsequent uplink transmissions, as described herein with reference to... Figure 4 Description. In this manner, a network node can perform a random access procedure 300 based on an additional uplink carrier 315-a. It should be noted that a network node can perform a random access procedure 300 based on an uplink carrier 310-a in a similar manner.

[0216] Random access procedure 301 can be an example of a two-step random access procedure based on an additional uplink carrier 315-b. A network node can be configured with a downlink carrier 305-b and an uplink carrier 310-b (which can be a cell's uplink and downlink carrier pair) and one or more additional uplink carriers 315 (including the additional uplink carrier 315-b). After determining the additional uplink carrier 315-b as a candidate uplink carrier for random access procedure 301, the network node can transmit Msg A 340 (e.g., a random access message) via the additional uplink carrier 315-b (the first candidate uplink carrier). Msg A 340 may include PRACH transmission. Based on Msg A 340, the network node can monitor the downlink channel for Msg B 345 (e.g., a downlink message, PDCCH) transmitted via the downlink carrier 305-b. In some respects, PDCCH monitoring can target a type 1 common search space set on the associated cell to obtain DCI format 1_0 with cyclic redundancy check (CRC) scrambled by MsgB-RNTI. This PDCCH monitoring can be a similar process for the additional uplink carrier 315-a as it is for the uplink carrier 310-a.

[0217] In some cases, based on a successful contention resolution at the end of the random access procedure 301, a network node may enter a connection mode with a second network node (e.g., a network entity) and send subsequent uplink transmissions, as described herein with reference to Figure 4 Description. In this manner, a network node can perform a random access procedure 301 based on an additional uplink carrier 315-b. It should be noted that a network node can perform a random access procedure 301 based on an uplink carrier 310-b in a similar manner.

[0218] Figure 4 An example of a communication framework 400 is shown that supports capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework for SUL and uplink CA (e.g., an eSUL framework). In some aspects, the communication framework 400 may implement aspects of wireless communication systems 100 and 200, or may be implemented by aspects of wireless communication systems 100 and 200. For example, a network node (e.g., UE 115, network entity 105) may use the communication framework 400 to convey uplink transmissions based on uplink carrier 410 or an additional uplink carrier 415 and a downlink carrier 405 of an associated cell.

[0219] As referenced in this article Figure 2 and Figure 3As described, a network node (e.g., UE 115) may be configured with a downlink carrier 405-a paired with an uplink carrier 410-a. Furthermore, the network node may be configured with one or more additional uplink carriers, which may be additional uplink carriers 415, including additional uplink carrier 415-a. Additional uplink carrier 415 may include an eSUL carrier, an SUL carrier in an SUL band, an uplink carrier in an FDD cell, carrier, or band, or uplink resources in a TDD cell, carrier, or band. The network node may use downlink carrier 405-a and a first candidate uplink carrier to perform as described herein. Figure 3 In the described random access procedure 420, the first candidate uplink carrier is determined to be either uplink carrier 410-a or an additional uplink carrier 415-a (a candidate uplink carrier selected from the associated cell). Based on the successful contention resolution at the end of the random access procedure 420, the network node can enter a connected mode (e.g., establish a radio connection with a network entity or other network nodes).

[0220] When in connected mode, a network node can determine a second candidate uplink carrier for uplink transmission. If the random access procedure is based on an additional uplink carrier 415-a, the network node can use either uplink carrier 410 (the normal uplink carrier) or the additional uplink carrier 415 for uplink transmission. For example, for uplink transmission 425-a, unless otherwise configured for the network node or indicated to the network node, the network node may default to using uplink carrier 410-b (paired with downlink carrier 405-b of the associated cell) instead of the additional uplink carrier 415-b. That is, the network node can determine uplink carrier 410-b as the second candidate uplink carrier based on the selection of additional uplink carrier 415-a as the first candidate uplink carrier for random access procedure 420. Therefore, the additional uplink carrier 415-b can be an additional uplink carrier used for uplink transmission 425-a.

[0221] In this scenario, the network node may transmit a feedback message (e.g., HARQ acknowledgment (ACK) feedback) for the reception of Msg4 or Msg B on the uplink carrier 410-b of the serving cell. That is, the network node may transmit the feedback message via uplink carrier 410-b in response to the end of the random access procedure 420, and also transmit uplink transmission 425-a via uplink carrier 410-b. Alternatively, the network node may transmit a feedback message (e.g., HARQ-ACK feedback) for the reception of Msg4 or Msg B on the additional uplink carrier 415-b of the serving cell. After transmitting the feedback message via the additional uplink carrier 415-b in response to the end of the random access procedure 420, the network node may return to transmitting uplink transmission 425-a via at least the uplink carrier 410-b of the cell (which is the default carrier). In such cases, uplink transmission 425-a may include one or more of the following: PUCCH transmission, PUSCH transmission scheduled by DCI format 0_0 via downlink carrier 405-b of the associated cell, or PRACH / Msg A transmission triggered by DCI format 1_0 via downlink carrier 405-b of the associated cell.

[0222] Alternatively, for uplink transmission 425-b, unless otherwise configured for or indicated to the network node, the network node may by default continue to use the additional uplink carrier 415-c (paired with the downlink carrier 405-c of the associated cell) instead of the uplink carrier 410-c. That is, the network node may determine the additional uplink carrier 415-c as the second candidate uplink carrier based on the selection of the additional uplink carrier 415-b as the first candidate uplink carrier for random access procedure 420. Therefore, the uplink carrier 410-c can be considered as the additional uplink carrier for uplink transmission 425-b.

[0223] In such cases, the network node may transmit a feedback message (e.g., HARQ-ACK feedback) for the reception of Msg4 or Msg B PDSCH on the additional uplink carrier 415-c of the serving cell. That is, the network node may transmit the feedback message via the additional uplink carrier 415-c in response to the end of the random access procedure 420, and also transmit uplink transmission 425-b via the additional uplink carrier 415-c. Uplink transmission 425-b may include one or more of the following: PUCCH transmission, PUSCH transmission scheduled by DCI format 0_0 via the downlink carrier 405-c of the associated cell, or PRACH / Msg A transmission triggered by DCI format 1_0 via the downlink carrier 405-c of the associated cell.

[0224] Figure 5 An example of a communication framework 500 is shown that supports capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework for SUL and uplink CA (e.g., an eSUL framework). In some aspects, the communication framework 500 may implement aspects of wireless communication systems 100 and 200, or may be implemented by aspects of wireless communication systems 100 and 200. For example, a network node (e.g., UE 115, network entity 105) may use the communication framework 500 to convey uplink transmissions based on uplink carrier 510 or an additional uplink carrier 515 and a downlink carrier 505 of an associated cell.

[0225] As referenced in this article Figure 2 and Figure 3 As described, a network node (e.g., UE 115) may be configured with a downlink carrier 505-a paired with an uplink carrier 510-a. Furthermore, the network node may be configured with one or more additional uplink carriers, which may be additional uplink carriers 515, including additional uplink carrier 515-a. Additional uplink carrier 515 may include an eSUL carrier, an SUL carrier in an SUL band, an uplink carrier in an FDD cell, carrier, or band, or uplink resources in a TDD cell, carrier, or band. The network node may use downlink carrier 505-a and a first candidate uplink carrier to perform as described herein. Figure 3 In the described random access procedure, the first candidate uplink carrier is determined to be either uplink carrier 510-a or an additional uplink carrier 515-a (a candidate uplink carrier selected from the associated cell). Based on the successful contention resolution at the end of the random access procedure 420, the network node can enter a connected mode (e.g., establish a radio connection with a network entity or other network nodes) and send uplink messages.

[0226] When in connected mode, a network node can use an additional uplink carrier 515 as a regular uplink component carrier for the uplink CA. That is, uplink carrier 510-a or additional uplink carrier 515-a can be selected as a second candidate uplink carrier for uplink transmission, which can be considered as an uplink component carrier for the uplink CA when the network node is in connected mode. Downlink carrier 505-a and uplink carrier 510-a, corresponding to the downlink and uplink carrier pair, can be associated with component carrier 520-a (e.g., CC#1), and additional uplink carrier 515-a, which only supports uplink communication, can be associated with component carrier 520-b (e.g., CC#2). In some cases, a second network node (e.g., a network entity) can schedule uplink transmissions on the cell's uplink carrier 510-a or additional uplink carrier 515-a (e.g., PUSCH 535).

[0227] In this scenario, uplink carrier 510-a and each additional uplink carrier 515 can be considered as regular uplink component carriers of the uplink CA scheduled by PDCCH 525 via downlink carrier 505-a of the associated cell. In some aspects, the timing and power control information for each of the uplink carrier 510-a and the additional uplink carrier 515 (e.g., each second candidate uplink carrier) can be based on downlink measurements from PDCCH 525 in downlink carrier 505-a. Furthermore, each of the uplink carrier 510-a and the additional uplink carrier 515 can be associated with a corresponding set of feedback procedures. That is, each uplink carrier 510 and each additional uplink carrier 515 can have its own HARQ space, independent of each other (this can be the same for the uplink CA).

[0228] In some aspects, network nodes can support simultaneous transmission across uplink carrier 510-a and additional uplink carrier 515-a based on UE capabilities (e.g., network node capabilities), and this can also be the case for uplink CA. In this way, network nodes can support combinations of one or more second candidate uplink carriers, which may include combinations of uplink carrier 510-a and one or more additional uplink carriers 515. In some aspects, network nodes can support uplink transmission handover on uplink carrier 510-a and additional uplink carrier 515 of the cell based on this capability (which may be the same as uplink CA uplink transmission handover). That is, network nodes can use this capability to switch the uplink transmission (Tx) chain to be used for uplink transmission from uplink carrier 510-a (second candidate uplink carrier) to additional uplink carrier 515-a (different second candidate uplink carrier), or network nodes can switch from additional uplink carrier 515-a to uplink carrier 510-a. Alternatively, network nodes can use this capability to switch the uplink Tx chain to be used for uplink transmission from one or more of uplink carrier 510-a and supplementary uplink carrier 515-a (e.g., an eSUL carrier). In some aspects, network nodes can use this capability to support half-duplex or full-duplex communication (same as uplink CA) between downlink carrier 505-a and each of uplink carrier 510-a and supplementary uplink carrier 515.

[0229] In some cases, uplink carrier 510-a and additional uplink carrier 515 can be scheduled by PDCCH 525 via downlink carrier 505-a of the associated cell, which is the same as uplink CA cross-carrier scheduling. In such cases, network nodes can monitor different sets of PDCCH candidates in the search space for different scheduled uplink carriers 510 and 515. Furthermore, DCI format 0_1 ​​or DCI format 0_2 may include a CIF field indicating which uplink transmission on uplink carrier 510-a or additional uplink carrier 515 the DCI format is scheduling. For example, if uplink carrier 510-a is selected as the default uplink carrier for uplink transmission (e.g., uplink carrier 410-a for uplink transmission 425-a, as referenced herein). Figure 4 As described, unless otherwise explicitly configured or indicated to the network node, PUCCH 540-a can be scheduled on uplink carrier 510-a (normal uplink carrier) by default.

[0230] In such cases, the CIF value (e.g., CIF#a) of DCI format 1_1 or DCI format 1_2 used to schedule PDSCH 530 on component carrier 520-a can be used for DCI format 0_1 ​​or DCI format 0_2 to schedule PUSCH 535-a on component carrier 520-a (via uplink carrier 510-a). In some aspects, the CIF value can be 0. Furthermore, different CIF values ​​can be assigned or configured for DCI format 0_1 ​​or DCI format 0_2 to schedule PUSCH 535-b on component carrier 520-b (via additional uplink carrier 515-a). In this respect, a network node may transmit multiple uplink transmissions via at least uplink carrier 510-a, wherein a first value of CIF#a for scheduling the PDSCH 530 on downlink carrier 505-a is the same as a second value of CIF#b for scheduling an uplink transmission via uplink carrier 510-a, and wherein the first value of CIF#a is different from a third value of CIF#c for scheduling another uplink transmission via additional uplink carrier 515-a.

[0231] Alternatively, if the additional uplink carrier 515-a is selected as the default uplink carrier for uplink transmission (e.g., the additional uplink carrier 415-c for uplink transmission 425-b, as referenced herein), Figure 4 As described, and if an uplink carrier 515-a is attached for a random access procedure when the network node is operating in idle mode, then PUCCH 540-b may be scheduled on the attached uplink carrier 515-a by default unless otherwise explicitly configured or indicated to the network node. In this way, PUSCH 535 may be dynamically scheduled by the DCI, and PUCCH 540 may be selected semi-statically.

[0232] In such cases, the CIF value (e.g., CIF#a) of DCI format 1_1 or DCI format 1_2 used to schedule PDSCH 530 on component carrier 520-a can be used to schedule PUSCH 535-b on component carrier 520-b using DCI format 0_1 ​​or DCI format 0_2 (via additional uplink carrier 515-a). In some aspects, the CIF value can be 0. Furthermore, different CIF values ​​can be assigned or configured to DCI format 0_1 ​​or DCI format 0_2 for scheduling PUSCH 535-a on component carrier 520-a (via uplink carrier 510-a). In this respect, a network node may transmit multiple uplink transmissions via one or more of at least one additional uplink carrier 515, wherein a first value of CIF#a for scheduling the PDSCH 530 on downlink carrier 505-a is the same as a second value of CIF#b for scheduling an uplink transmission via one of the additional uplink carriers 515-a, and wherein the first value of CIF#a is different from a third value of CIF#c for scheduling another uplink transmission via another additional uplink carrier 515.

[0233] Figure 6 An example of a carrier configuration 600 supporting capability signaling (e.g., eSUL framework) for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. In some aspects, the carrier configuration 600 may implement, or may be implemented by, aspects of wireless communication systems 100 and 200. For example, a network node (e.g., UE 115, network entity 105) may communicate via the carrier and frequency band 605 illustrated in the carrier configuration 600.

[0234] A first network node (e.g., UE 115) may support communication on NR bands or combinations of NR bands (e.g., band 605). The first network node may report to a second network node (e.g., a network entity) a list of bands 605 that the first network node can use to communicate with the second network node. For each band 605, the first network node may additionally indicate support for optional features. Additionally or alternatively, the first network node may report a list of band combinations that the first network node can be configured to have a CA with the second network node. Furthermore, for each band combination, the first network node may indicate support for optional features.

[0235] For example, the first network node may support communication using downlink and uplink carriers on cells in band n79 or band n3 (e.g., the corresponding downlink and uplink cells). In some other cases, the first network node may support communication using downlink and uplink carriers on cells in band n79 and band n3. In some aspects, the first network node may support CA utilizing a combination of the bands n79 and n3. That is, the first network node may support CA using downlink carriers, uplink carriers, or both uplink and downlink carriers in bands n79 and n3. Additionally, the first network node may support optional features of CA in cells in bands n79 and n3.

[0236] As referenced in this article Figure 2 As described, a first network node (e.g., UE 115) can transmit capability information indicating the ability to communicate using a pair of carriers in different frequency bands 605 or the same frequency band 605. This pair of carriers can be an uplink and downlink carrier pair, where the uplink carrier can be a normal uplink carrier or an eSUL carrier. For example, the first network node can support communication using a downlink carrier in frequency band n79 and an uplink carrier in frequency band n3. Furthermore, the first network node can support communication using SDL carriers in different frequency bands and cells in uplink and eSUL carrier pairs.

[0237] In some respects, the first network node may support communication in bands 605-a and 605-b. In such cases, the first network node may support communication via a downlink carrier of a TDD or FDD cell or band, an uplink carrier of that cell, and one or more eSUL carriers as uplink carriers of the same TDD, FDD, or SUL cell or band, or uplink carriers of different TDD, FDD, or SUL cells or bands. For example, band 605-a may be band n79 for TDD, which may be associated with a spectrum of approximately 4.5 GHz. Because the first network node supports band 605-a, the first network node may support TDD operation and therefore may support both downlink reception (via downlink (DL) carrier) and uplink transmission (via uplink (UL) carrier) for band 605-a. Furthermore, band 605-b may be band n3 for FDD, which may be associated with a spectrum of approximately 1.8 GHz. By supporting band 605-b, the first network node can support FDD operation, and therefore can support both downlink reception (via downlink carrier) and uplink transmission (via eSUL carrier) for band 605-b.

[0238] In some aspects, the first network node may support communication via downlink and uplink carriers in the same frequency band 605 (e.g., TDD operation in frequency band 605-a). Additionally, the first network node may support optional features of cells in frequency bands n79 and n3. Alternatively, the first network node may support communication via downlink and eSUL carriers in different frequency bands (e.g., downlink carriers in frequency band 605-a and eSUL carriers in frequency band 605-b).

[0239] In some other examples, the first network node may support communication in bands 605-c, 605-d, and 605-e. In such cases, the first network node may support communication via a downlink carrier of an SDL cell or band and one or more eSUL carriers, which may be uplink carriers of other TDD, FDD, or SUL cells or bands. For example, band 605-c may be band n41 for TDD, which may be associated with a spectrum of approximately 2.5 GHz. Furthermore, band 605-e may be band n29 for SDL, which may be associated with a spectrum of approximately 720 MHz. In such cases, the first network node may support a pair of carriers including an eSUL carrier (for uplink transmission) and an SDL carrier (for downlink reception). In some aspects, the first network node may support uplink communication using the eSUL band and downlink communication using the SDL band (e.g., FDD operation in bands 605-d and 605-e). In other words, the eSUL carrier can be paired with an SDL carrier on the same or different frequency bands 605.

[0240] In some other examples, the first network node may support communication in both band 605-f and band 605-g. In such cases, the first network node may support communication via an uplink carrier of a TDD, FDD, or SUL cell or band, which is configured as a normal uplink carrier or eSUL carrier for more than one downlink carrier of a TDD, FDD, or SUL cell or band. For example, band 605-f may be band n41 for TDD, which may be associated with a spectrum of approximately 2.5 GHz. In some aspects, the first network node may support uplink and downlink communication using band 605-f, or downlink communication using band 605-g and uplink communication using band 605-f. That is, the uplink carrier (e.g., an eSUL carrier) and the downlink carrier may be in different bands 605 and may be paired to enable FDD operation.

[0241] Figure 7An example of a process flow 700 is shown that supports capability signaling for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework (e.g., an eSUL framework) for SUL and uplink CA. Process flow 700 can implement aspects of wireless communication systems 100 and 200, or can be implemented by aspects of wireless communication systems 100 and 200. For example, process flow 700 may exemplify operations between network node 705-a (e.g., UE 115) and network node 705-b (e.g., network entity 105), which may be examples of the corresponding devices described herein. In the following description of process flow 700, operations between network node 705-a and network node 705-b may be transmitted in a different order than the example order shown, or operations performed by network node 705-a and network node 705-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0242] At 710, network node 705-a can receive from network node 705-b first information indicating first resources for network node 705-a to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. The first information may be sent in a broadcast message (e.g., SIB1) or a dedicated message (e.g., higher-layer signaling).

[0243] At 715, network node 705-a can receive from network node 705-b second information indicating second resources for network node 705-a to use for communication via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers. The second uplink carrier may include an additional SUL carrier or an eSUL carrier, which may be considered and used as an SUL carrier when network node 705-a is in idle mode, and considered and used as an uplink component carrier in the uplink CA when network node 705-a is in idle mode.

[0244] At 720, network node 705-a, while in idle mode, can determine a first candidate uplink carrier for the random access procedure from a group of multiple candidate uplink carriers. The first candidate uplink carrier can be determined as a first uplink carrier (e.g., a normal uplink carrier) or a second uplink carrier (e.g., an eSUL carrier) among the second uplink carriers.

[0245] At point 725, network node 705-a can perform a random access procedure using a first candidate uplink carrier and a first downlink carrier, wherein the first uplink carrier or one of one or more second uplink carriers is the first candidate uplink carrier. In other words, network node 705-a can perform a 4-step or 2-step random access procedure based on a normal uplink carrier or an eSUL carrier and a downlink carrier of the associated cell.

[0246] At point 730, network node 705-b can participate in the random access procedure with network node 705-a using a first candidate uplink carrier and a first downlink carrier, wherein the first uplink carrier or one of one or more second uplink carriers is the first candidate uplink carrier. In other words, network node 705-b can participate in a 4-step or 2-step random access procedure based on a normal uplink carrier or an eSUL carrier and a downlink carrier of the associated cell.

[0247] At point 735, network node 705-a, when in connected mode, can determine a second candidate uplink carrier from a group of candidate uplink carriers for uplink transmission. In some aspects, this second candidate uplink carrier can be one of a group of candidate uplink carriers used for a set of multiple uplink transmissions. This second candidate uplink carrier can be a normal uplink carrier or an eSUL carrier, depending on which type of uplink carrier was used in the random access procedure.

[0248] At 740, network node 705-a may send an uplink transmission to network node 705-b via the determined second candidate uplink carrier after the random access procedure (e.g., based on a successful contention resolution) and while network node 705-a is still in connected mode. In some aspects, the uplink transmission may occur using different component carriers depending on whether the second candidate uplink carrier is a normal uplink carrier or an eSUL carrier.

[0249] Figure 8An example of a process flow 800 supporting capability signaling (e.g., eSUL framework) for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. Process flow 800 may implement aspects of wireless communication systems 100 and 200, or may be implemented through aspects of wireless communication systems 100 and 200. For example, process flow 800 may exemplify operations between network node 805-a (e.g., UE 115) and network node 805-b (e.g., network entity 105), which may be examples of the corresponding devices described herein. In the following description of process flow 800, operations between network node 805-a and network node 805-b may be transmitted in a different order than the example order shown, or operations performed by network node 805-a and network node 805-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 800, and other operations may be added to process flow 800.

[0250] At 810, network node 805-a can receive capability information from network node 805-b. This capability information may indicate the ability of network node 805-a to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier (e.g., a normal uplink carrier, eSUL) in a second frequency band different from the first frequency band. Alternatively, the capability information may indicate the ability of network node 805-a to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier in the first frequency band and a first uplink carrier in the first frequency band.

[0251] At point 815, network node 805-a can send carrier information based on the capability information to network node 805-b. If the capability information indicates the capability of network node 805-a to communicate using a pair of carriers in different frequency bands, the carrier information can indicate one or more downlink carriers and one or more uplink carriers for wireless communication by network node 805-a, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include a first uplink carrier. Alternatively, if the capability information indicates the capability of network node 805-a to communicate using a pair of carriers in the same frequency band, the carrier information can indicate one or more downlink carriers and one or more uplink carriers for wireless communication by network node 805-a, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include a first uplink carrier and a second uplink carrier in the first frequency band, and wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. That is, the second carrier information can identify the eSUL carrier.

[0252] At 820, network node 805-a may receive from network node 805-b first information indicating first resources for network node 805-a to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier. At 825, network node 805-a may receive from network node 805-b second information indicating second resources for network node 805-a to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers together constitute a group of multiple candidate uplink carriers. Network node 805-a may use the candidate uplink carriers for random access procedures or uplink transmissions.

[0253] At 830, network node 805-a may participate in (e.g., with network node 805-b) wireless communication via a first downlink carrier and a first uplink carrier (e.g., a normal uplink carrier) or a second uplink carrier (e.g., an eSUL carrier) based on applicable carrier information.

[0254] Figure 9A block diagram 900 illustrates a device 905 that supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands, and also supports a framework (e.g., an eSUL framework) for SUL and uplink CA, according to one or more aspects of this disclosure. Device 905 may be an example of aspects of UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0255] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the framework for SUL and uplink CA and capability signaling for downlink and uplink carriers and cells in different frequency bands). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0256] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels, such as packets, user data, control information, or any combination thereof, relating to the framework for SUL and uplink CA and capability signaling for downlink and uplink carriers and cells in different frequency bands. In some aspects, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0257] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the framework for SUL and uplink CA as described herein, as well as capability signaling for downlink and uplink carriers and cells in different frequency bands. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0258] In some aspects, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, digital signal processors (DSPs), central processing units (CPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, microcontrollers, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some aspects, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0259] Additionally or alternatively, in some aspects, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0260] In some respects, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0261] For example, the communication manager 920 can be configured or operable to support components for receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. The communication manager 920 can be configured or operable to support components for receiving second information indicating a second resource for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a set of multiple candidate uplink carriers. The communication manager 920 can be configured or operable to support components for determining a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers when the first network node is in idle mode. The communication manager 920 can be configured or operable to support components for determining a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers when the first network node is in connected mode.

[0262] For example, the communication manager 920 can be configured or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. The communication manager 920 can be configured or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, wherein the carrier information is based on the capability information. The communication manager 920 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0263] For example, the communication manager 920 can be configured or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. The communication manager 920 can be configured or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. The communication manager 920 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0264] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., a control receiver 910, transmitter 915, communication manager 920, or a combination thereof, or a processor otherwise coupled to them) can support a unified framework for SUL and uplink CA, as well as capability signaling techniques for downlink and uplink carriers and cells in different frequency bands, which can reduce latency, improve spectrum efficiency, improve resource utilization efficiency, increase signaling capacity, and improve communication between network nodes.

[0265] Figure 10 A block diagram 1000 of device 1005 supporting a framework (e.g., an eSUL framework) for SUL and uplink CA according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or UE 115 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0266] Receiver 1010 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the framework for SUL and uplink CA). The information may be transmitted to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0267] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to the framework for SUL and uplink CA), such as packets, user data, control information, or any combination thereof. In some aspects, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0268] Device 1005 or its various components may be examples of parts used to perform various aspects of the framework for SUL and uplink CA as described herein. For example, communication manager 1020 may include carrier pair component 1025, SUL carrier component 1030, random access component 1035, uplink component 1040, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some aspects, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0269] Carrier pair component 1025 is capable of, configured to, or operable to support components for receiving first information indicating first resources for a first network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band. SUL carrier component 1030 is capable of, configured to, or operable to support components for receiving second information indicating second resources for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a set of multiple candidate uplink carriers. Random access component 1035 is capable of, configured to, or operable to support components for determining a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers when the first network node is in idle mode. Uplink component 1040 is capable of, configured to, or operable to support components for determining a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers when the first network node is in connected mode.

[0270] Figure 11A block diagram 1100 of a communication manager 1120 supporting a framework for SUL and uplink CA (e.g., an eSUL framework) according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of the framework for SUL and uplink CA as described herein. For example, the communication manager 1120 may include a carrier pair component 1125, an SUL carrier component 1130, a random access component 1135, an uplink component 1140, a messaging component 1145, a receive power component 1150, a feedback component 1155, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0271] Carrier pair component 1125 is capable of, configured to, or operable to support components for receiving first information indicating first resources for a first network node to communicate via a first uplink carrier and at least one of a first downlink carrier paired with the first uplink carrier in the same frequency band. SUL carrier component 1130 is capable of, configured to, or operable to support components for receiving second information indicating second resources for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a group of candidate uplink carriers. Random access component 1135 is capable of, configured to, or operable to support components for determining a first candidate uplink carrier for a random access procedure from the group of candidate uplink carriers when the first network node is in idle mode. Uplink component 1140 is capable of, configured to, or operable to support components for determining a second candidate uplink carrier for uplink transmission from the group of candidate uplink carriers when the first network node is in connected mode.

[0272] In some aspects, to support the reception of second information, message component 1145 is capable of, configured to, or operable to support components for receiving broadcast or dedicated messages including second information, wherein the second information indicates at least one of the following: frequency information of each of one or more second uplink carriers, uplink bandwidth portion information of each of one or more second uplink carriers, or timer information relating to time alignment of each of one or more second uplink carriers. In some aspects, the second information includes criteria for determining a first candidate uplink carrier by the first network node.

[0273] In some aspects, to support the determination of a first candidate uplink carrier, the receive power component 1150 can be configured or operable to support components for determining a receive power value. In some aspects, to support the determination of a first candidate uplink carrier, the receive power component 1150 can be configured or operable to support components for determining a first uplink carrier or one of a plurality of second uplink carriers as a first candidate uplink carrier based on a first comparison of the receive power value with a first receive power threshold.

[0274] In some aspects, the standard includes one or more second receive power thresholds and an association between each of the one or more second uplink carriers and a corresponding receive power value range, each corresponding receive power value range being defined by at least one of the one or more second receive power thresholds.

[0275] In some respects, determining a first candidate uplink carrier from one or more second uplink carriers is based on a second comparison of a received power value with one or more second received power thresholds.

[0276] In some respects, the random access component 1135 is capable of, can be configured to, or is operable to support components for performing a random access procedure using a first candidate uplink carrier and a first downlink carrier, wherein one of one or more second uplink carriers is the first candidate uplink carrier.

[0277] In some aspects, to support the execution of a random access procedure, the random access component 1135 can be configured or operable to support components for transmitting a random access message via a first candidate uplink carrier. In some aspects, to support the execution of a random access procedure, the random access component 1135 can be configured or operable to support components for monitoring the downlink channel in response to a random access response message transmitted via a first downlink carrier, wherein the random access response message is scheduled for transmission of an uplink shared channel message via the first candidate uplink carrier. In some aspects, to support the execution of a random access procedure, the random access component 1135 can be configured or operable to support components for transmitting an uplink shared channel message via a first candidate uplink carrier based on a random access response message. In some aspects, to support the execution of a random access procedure, the random access component 1135 can be configured or operable to support components for receiving a contention-resolving downlink message via a first downlink carrier based on an uplink shared channel message.

[0278] In some aspects, to support the execution of a random access procedure, the random access component 1135 can be, configured, or operated to support components for transmitting random access messages via a first candidate uplink carrier. In some aspects, to support the execution of a random access procedure, the random access component 1135 can be, configured, or operated to support components for monitoring the downlink channel based on the random access message for downlink messages transmitted via the first downlink carrier.

[0279] In some respects, in order to support the determination of a second candidate uplink carrier, uplink component 1140 is capable of, configured to, or operable to support components for determining a first uplink carrier as a second candidate uplink carrier, wherein the determination of the first uplink carrier is based on one of one or more second uplink carriers being determined as a first candidate uplink carrier for a random access procedure.

[0280] In some aspects, feedback component 1155 can be configured or operated to support components for transmitting a feedback message via a first uplink carrier in response to the end of a random access procedure. In some aspects, uplink component 1140 can be configured or operated to support components for transmitting uplink transmissions via at least a first uplink carrier.

[0281] In some aspects, feedback component 1155 is capable of, configured to, or operable to support components for transmitting a feedback message via a first candidate uplink carrier in response to the end of a random access procedure. In some aspects, uplink component 1140 is capable of, configured to, or operable to support components for transmitting uplink transmissions via at least a first candidate uplink carrier.

[0282] In some respects, uplink component 1140 is capable of, configured to, or operable to support components for transmitting the group of multiple uplink transmissions via at least a first uplink carrier, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on the first downlink carrier is the same as a second value of a second carrier information field for scheduling uplink transmissions via one uplink of the first uplink carrier in the group of multiple uplink transmissions, and wherein the first value is different from a third value of a third carrier information field for scheduling uplink transmissions via another uplink of one or more second uplink carriers in the group of multiple uplink transmissions.

[0283] In some respects, to support the determination of a second candidate uplink carrier, uplink component 1140 is capable of, configured to, or operable to support components for determining one of one or more second uplink carriers as a second candidate uplink carrier, wherein the determination of that one of the one or more second uplink carriers is based on the determination of that one of the one or more second uplink carriers as a first candidate uplink carrier for a random access procedure.

[0284] In some aspects, uplink component 1140 is capable of, configured to, or operable to support components for transmitting the group of multiple uplink transmissions via the one of the one or more second uplink carriers, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on a first downlink carrier is different from a second value of a second carrier information field for scheduling uplink transmissions via the one of the one or more second uplink carriers in the group of multiple uplink transmissions, and wherein the first value is different from a third value of a third carrier information field for scheduling uplink transmissions via another uplink transmission of another of the one or more second uplink carriers in the group of multiple uplink transmissions.

[0285] In some aspects, feedback component 1155 is capable of, configured to, or operable to support components for transmitting a feedback message via one of the one or more second uplink carriers in response to the end of a random access procedure. In some aspects, uplink component 1140 is capable of, configured to, or operable to support components for transmitting uplink transmissions via at least one of the one or more second uplink carriers.

[0286] In some aspects, uplink transmission includes one or more of uplink control channel messages, uplink shared channel messages, or random access channel messages. In some aspects, the second candidate uplink carrier is an uplink component carrier used for CA when the first network node is in connected mode.

[0287] In some aspects, the second candidate uplink carrier is associated with a corresponding set of feedback procedures. In some aspects, the combination of one or more second candidate uplink carriers, including the second candidate uplink carrier, is based on the capabilities of the first network node.

[0288] In some respects, uplink component 1140 is capable of, configured to, or operable to support components for switching from the second candidate uplink carrier to a different second candidate uplink carrier based on the capability of the first network node.

[0289] In some respects, the second candidate uplink carrier is scheduled based on downlink messages associated with the same cell. In other respects, half-duplex or full-duplex operation between the first downlink carrier and the second candidate uplink carrier is based on the capabilities of the first network node.

[0290] In some aspects, the first uplink carrier and one or more second uplink carriers are in different frequency bands. In other aspects, the first uplink carrier and one or more second uplink carriers are in the same frequency band.

[0291] In some aspects, the first uplink carrier and one or more second uplink carriers are used for communication between the first network node and different cells. In other aspects, the first uplink carrier and one or more second uplink carriers are used for communication between the first network node and the same cell.

[0292] In some aspects, idle mode and connected mode are communication states of the first network node relative to the second network node, wherein communication during connected mode is allocated for resources used by the first network node, and communication during idle mode is allocated for resources used by the shared network node. In some aspects, the second candidate uplink carrier is one of a plurality of second candidate uplink carriers in a group of candidate uplink carriers.

[0293] Figure 12 A block diagram 1200 of device 1205 supporting capability signaling for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of aspects of device 1005 or UE 115 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205 or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220) may also include at least one communication interface and at least one processor coupled to the communication interface to support the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0294] Receiver 1210 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to capability signaling for downlink and uplink carriers and cells in different frequency bands). The information may be passed to other components of device 1205. Receiver 1210 may utilize a single antenna or a collection of antennas.

[0295] Transmitter 1215 may provide components for transmitting signals generated by other components of device 1205. For example, transmitter 1215 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to capability signaling for downlink and uplink carriers and cells in different frequency bands), such as packets, user data, control information, or any combination thereof. In some aspects, transmitter 1215 may be co-located with receiver 1210 in a transceiver module. Transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0296] Device 1205 or its various components may be examples of parts used to perform various aspects of capability signaling for downlink and uplink carriers and cells in different frequency bands as described herein. For example, communication manager 1220 may include capability information component 1225, carrier information component 1230, wireless communication component 1235, carrier determination component 1240, or any combination thereof. Communication manager 1220 may be examples of various aspects of communication manager 1220 as described herein. In some aspects, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0297] Capability information component 1225 is capable of, configured to, or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Carrier information component 1230 is capable of, configured to, or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, and wherein the carrier information is based on the capability information. Wireless communication component 1235 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0298] Capability information component 1225 is capable of, configured to, or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. Carrier determination component 1240 is capable of, configured to, or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. Wireless communication component 1235 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on carrier information.

[0299] Figure 13 A block diagram 1300 of a communication manager 1320 supporting capability signaling for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. The communication manager 1320 may be an example of a communication manager 1320, a communication manager 1220, or aspects thereof as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of capability signaling for downlink and uplink carriers and cells in different frequency bands as described herein. For example, the communication manager 1320 may include a capability information component 1325, a carrier information component 1330, a wireless communication component 1335, a carrier determination component 1340, a resource component 1345, a random access component 1350, an uplink transmission component 1355, or any combination thereof. Each of these components, or components of its sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0300] Capability information component 1325 is capable of, configured to, or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Carrier information component 1330 is capable of, configured to, or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, wherein the carrier information is based on the capability information. Wireless communication component 1335 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0301] In some aspects, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band. In some aspects, the capability of the first network node to communicate using the carrier pair is indicated by the first and second indications.

[0302] In some aspects, the capability information includes: a first list of individual frequency bands, wherein the first network node supports both downlink and uplink communication via each of these individual frequency bands; and a second list of frequency band pairs, wherein for each pair, the first network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with that downlink communication via a second pair of components in the corresponding pair. In some aspects, the first frequency band and the second frequency band are one of the frequency band pairs included in the second list.

[0303] In some aspects, the capability information indicates one or more first sets of features supported by the first network node and one or more second sets of features supported by the first network node. In some aspects, a single set of features from the one or more first sets is associated with a corresponding downlink frequency band in a second list of frequency band pairs. In some aspects, a single set of features from the one or more second sets is associated with a corresponding uplink frequency band in a second list of frequency band pairs. In some aspects, the capability information indicates one or more first sets of features and one or more second sets of features separate from a third set of features supported by the first network node and each associated with a corresponding individual frequency band from the first list.

[0304] In some aspects, the capability information includes a list of individual frequency bands, wherein the first network node supports both downlink and uplink communication via each of these individual frequency bands. In some aspects, the list includes an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list of individual frequency bands. In some aspects, a second frequency band is included in an additional set of uplink frequency bands within the additional set of uplink frequency bands, wherein the corresponding individual frequency band belonging to that additional set of uplink frequency bands is the first frequency band.

[0305] In some aspects, the capability information indicates one or more first sets of features supported by the first network node and each associated with a corresponding individual frequency band from the list. In some aspects, the capability information also indicates one or more second sets of features supported by the first network node and each associated with at least one uplink frequency band from a corresponding set in an additional set of uplink frequency bands.

[0306] In some respects, the first frequency band is the TDD band. In other respects, the second frequency band is the FDD band or the SUL band.

[0307] In some respects, one or more downlink carriers include SDL carriers. In some respects, the first frequency band is an SDL frequency band that includes SDL carriers.

[0308] In some aspects, to support receiving carrier information, resource component 1345 is capable of, configured to, or operable to support means for receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier. In some aspects, to support receiving carrier information, resource component 1345 is capable of, configured to, or operable to support means for receiving second information indicating a second resource for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a group of multiple candidate uplink carriers.

[0309] In some aspects, to support participation in wireless communication, the random access component 1350 is capable of, configured to, or operable to support components for determining a first candidate uplink carrier from a set of multiple candidate uplink carriers for the random access procedure when the first network node is in idle mode. In some aspects, to support participation in wireless communication, the uplink transmission component 1355 is capable of, configured to, or operable to support components for determining a second candidate uplink carrier from a set of multiple candidate uplink carriers for uplink transmission when the first network node is in connected mode.

[0310] In some respects, idle mode and connected mode are communication states of the first network node relative to the second network node. In some respects, communication during connected mode is for resources allocated for use by the first network node. In some respects, communication during idle mode is for resources allocated for use by the shared network node.

[0311] In some aspects, capability information component 1325 is capable of, configured to, or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. Carrier determination component 1240 is capable of, configured to, or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. In some aspects, wireless communication component 1335 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on carrier information.

[0312] In some aspects, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band. In some aspects, the capability of the first network node to communicate using the carrier pair is indicated by the first and second indications.

[0313] In some respects, the second uplink carrier is a SUL carrier when the first network node is in idle mode, and an uplink component carrier for CA when the first network node is in connected mode.

[0314] In some aspects, to support receiving carrier information, resource component 1345 is capable of, configured to, or operable to support means for receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier. In some aspects, to support receiving carrier information, resource component 1345 is capable of, configured to, or operable to support means for receiving second information indicating a second resource for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a group of multiple candidate uplink carriers.

[0315] In some aspects, to support participation in wireless communication, the random access component 1350 is capable of, configured to, or operable to support components for determining a first candidate uplink carrier from a set of multiple candidate uplink carriers for the random access procedure when the first network node is in idle mode. In some aspects, to support participation in wireless communication, the uplink transmission component 1355 is capable of, configured to, or operable to support components for determining a second candidate uplink carrier from a set of multiple candidate uplink carriers for uplink transmission when the first network node is in connected mode.

[0316] In some respects, idle mode and connected mode are communication states of the first network node relative to the second network node. In some respects, communication during connected mode is on resources allocated for use by the first network node. In some respects, communication during idle mode is on resources allocated for use by the shared network node. In some respects, the first frequency band is a TDD frequency band.

[0317] Figure 14A diagram of a system 1400 is shown, comprising device 1405 supporting capability signaling for downlink and uplink carriers and cells in different frequency bands and also supporting a framework (e.g., an eSUL framework) for SUL and uplink CA, according to one or more aspects of this disclosure. Device 1405 may be an example of device 905, device 1005, or UE 115 as described herein, or a component including such devices. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1405 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1420, an input / output (I / O) controller 1410, a transceiver 1415, an antenna 1425, a memory 1430, a code 1435, and a processor 1440. These components may be electronically communicated or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, or electrically) via one or more buses (e.g., bus 1445).

[0318] I / O controller 1410 manages the input and output signals of device 1405. I / O controller 1410 can also manage peripheral devices not integrated into device 1405. In some cases, I / O controller 1410 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1410 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1410 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1410 may be implemented as part of a processor, such as processor 1440. In some cases, a user may interact with device 1405 via the I / O controller 1410 or through hardware components controlled by the I / O controller 1410.

[0319] In some cases, device 1405 may include a single antenna 1425. However, in other cases, device 1405 may have more than one antenna 1425 capable of concurrently transmitting or receiving multiple wireless transmissions. As described herein, transceiver 1415 may communicate bidirectionally via one or more antennas 1425, a wired or wireless link. For example, transceiver 1415 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1415 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1425 for transmission; and demodulating packets received from one or more antennas 1425. Transceiver 1415, or transceiver 1415 and one or more antennas 1425, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or any component thereof as described herein.

[0320] Memory 1430 may include random access memory (RAM) and read-only memory (ROM). Memory 1430 may store computer-readable, computer-executable code 1435, including instructions that, when executed by processor 1440, cause device 1405 to perform the various functions described herein. Code 1435 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1435 may not be directly executable by processor 1440, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 1430 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0321] Processor 1440 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1440 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks supporting frameworks for SUL and uplink CA, and capability signaling for downlink and uplink carriers and cells in different frequency bands). For example, device 1405 or components of device 1405 may include processor 1440 and memory 1430 coupled to or coupled to processor 1440, processor 1440 and memory 1430 being configured to perform the various functions described herein.

[0322] For example, the communication manager 1420 can be configured or operable to support components for receiving first information indicating first resources for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. The communication manager 1420 can be configured or operable to support components for receiving second information indicating second resources for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a set of multiple candidate uplink carriers. The communication manager 1420 can be configured or operable to support components for determining a first candidate uplink carrier for a random access procedure from the set of multiple candidate uplink carriers when the first network node is in idle mode. The communication manager 1420 can be configured or operable to support components for determining a second candidate uplink carrier for uplink transmission from the set of multiple candidate uplink carriers when the first network node is in connected mode.

[0323] For example, the communication manager 720 can be configured or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. The communication manager 720 can be configured or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, wherein the carrier information is based on the capability information. The communication manager 720 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0324] For example, the communication manager 720 can be configured or operable to support components for transmitting capability information indicating the capability of a first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. The communication manager 720 can be configured or operable to support components for receiving carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the first network node, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. The communication manager 720 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on the carrier information.

[0325] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support a unified framework for SUL and uplink CA, as well as capability signaling techniques for downlink and uplink carriers and cells in different frequency bands. These techniques can reduce latency, improve spectrum efficiency, improve resource utilization efficiency, increase signaling capacity, and improve communication between network nodes.

[0326] In some respects, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1415, one or more antennas 1425, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1440, memory 1430, code 1435, or any combination thereof. For example, code 1435 may include instructions that can be executed by the processor 1440 to cause the device 1405 to perform various aspects of the framework for SUL and uplink CA as described herein, as well as capability signaling for downlink and uplink carriers and cells in different frequency bands, or the processor 1440 and memory 1430 may be otherwise configured to perform or support such operations.

[0327] Figure 15 A block diagram 1500 of device 1505 is shown, which supports signaling capabilities for downlink and uplink carriers and cells in different frequency bands according to one or more aspects of this disclosure, and also supports a framework (e.g., an eSUL framework) for SUL and uplink CA. Device 1505 may be an example of aspects of network entity 105 as described herein. Device 1505 may include receiver 1510, transmitter 1515, and communication manager 1520. Device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0328] Receiver 1510 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1505. In some aspects, receiver 1510 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0329] Transmitter 1515 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1505. For example, transmitter 1515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some aspects, transmitter 1515 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1515 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some aspects, transmitter 1515 and receiver 1510 may be co-located in a transceiver, which may include or be coupled to a modem.

[0330] The communication manager 1520, receiver 1510, transmitter 1515, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the framework for SUL and uplink CA as described herein, as well as capability signaling for downlink and uplink carriers and cells in different frequency bands. For example, the communication manager 1520, receiver 1510, transmitter 1515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0331] In some aspects, the communication manager 1520, receiver 1510, transmitter 1515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs or other programmable logic devices, microcontrollers, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some aspects, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0332] Additionally or alternatively, in some examples, the communication manager 1520, receiver 1510, transmitter 1515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1520, receiver 1510, transmitter 1515, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0333] In some respects, the communication manager 1520 may be configured to use or otherwise cooperate with the receiver 1510, the transmitter 1515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1520 may receive information from the receiver 1510, transmit information to the transmitter 1515, or be integrated in combination with the receiver 1510, the transmitter 1515, or both to acquire information, output information, or perform various other operations as described herein.

[0334] For example, the communication manager 1520 can be configured or operable to support components for transmitting first information indicating first resources for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. The communication manager 1520 can be configured or operable to support components for transmitting second information indicating second resources for a second network node to communicate via one or more second uplink carriers associated with but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively form a set of candidate uplink carriers. The communication manager 1520 can be configured or operable to support components for participating in a random access procedure with the second network node using a first candidate uplink carrier from the set of candidate uplink carriers. The communication manager 1520 can be configured or operable to support components for receiving uplink transmissions via second candidate uplink carriers from the set of candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0335] For example, the communication manager 920 can be configured or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. The communication manager 920 can be configured or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the second network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, wherein the carrier information is based on the capability information. The communication manager 920 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0336] For example, the communication manager 920 can be configured or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. The communication manager 920 can be configured or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by a first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. The communication manager 920 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on the carrier information.

[0337] By including or configuring a communication manager 1520 according to an example as described herein, device 1505 (e.g., controlling receiver 1510, transmitter 1515, communication manager 1520, or a combination thereof, or a processor otherwise coupled to them) can support a unified framework for SUL and uplink CA, as well as capability signaling techniques for uplink and downlink carriers in different frequency bands, which can reduce latency, improve spectrum efficiency, improve resource utilization efficiency, increase signaling capacity, and improve communication between network nodes.

[0338] Figure 16A block diagram 1600 of device 1605 supporting capability signaling (eSUL framework) for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. Device 1605 may be an example of aspects of device 1505 or network entity 105 as described herein. Device 1605 may include receiver 1610, transmitter 1615, and communication manager 1620. Device 1605 may also include a processor. Each of these components may communicate with each other, for example, via one or more buses.

[0339] Receiver 1610 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1605. In some aspects, receiver 1610 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1610 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0340] Transmitter 1615 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1605. For example, transmitter 1615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some aspects, transmitter 1615 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1615 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some aspects, transmitter 1615 and receiver 1610 may be co-located in a transceiver, which may include or be coupled to a modem.

[0341] Device 1605 or its various components may be examples of parts used to perform various aspects of the framework for SUL and uplink CA as described herein. For example, communication manager 1620 may include carrier pair manager 1625, SUL carrier manager 1630, random access manager 1635, uplink transmission manager 1640, or any combination thereof. Communication manager 1620 may be examples of aspects of communication manager 1520 as described herein. In some aspects, communication manager 1620 or its various components may be configured to use or otherwise cooperate with receiver 1610, transmitter 1615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1620 may receive information from receiver 1610, transmit information to transmitter 1615, or be integrated in combination with receiver 1610, transmitter 1615, or both to acquire information, output information, or perform various other operations as described herein.

[0342] Carrier pair manager 1625 is capable of, configured to, or operable to support components for transmitting first information indicating a first resource for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. SUL carrier manager 1630 is capable of, configured to, or operable to support components for transmitting second information indicating a second resource for a second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of candidate uplink carriers. Random access manager 1635 is capable of, configured to, or operable to support components for participating in a random access procedure with the second network node using a first candidate uplink carrier from a set of candidate uplink carriers. Uplink transmission manager 1640 is capable of, configured to, or operable to support components for receiving uplink transmissions via second candidate uplink carriers from a set of candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0343] Figure 17A block diagram 1700 illustrates a communication manager 1720 supporting a framework (e.g., an eSUL framework) for SUL and uplink CA according to one or more aspects of this disclosure. The communication manager 1720 may be an example of a communication manager 1520, a communication manager 1620, or aspects thereof as described herein. The communication manager 1720 or its various components may be examples of parts for performing various aspects of the framework for SUL and uplink CA as described herein. For example, the communication manager 1720 may include a carrier pair manager 1725, an SUL carrier manager 1730, a random access manager 1735, an uplink transmission manager 1740, a message manager 1745, a feedback manager 1750, a CIF manager 1755, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between the protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0344] Carrier pair manager 1725 is capable of, configured to, or operable to support components for transmitting first information indicating a first resource for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. SUL carrier manager 1730 is capable of, configured to, or operable to support components for transmitting second information indicating a second resource for a second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a set of candidate uplink carriers. Random access manager 1735 is capable of, configured to, or operable to support components for participating in a random access procedure with the second network node using a first candidate uplink carrier from a set of candidate uplink carriers. Uplink transmission manager 1740 is capable of, configured to, or operable to support components for receiving uplink transmissions via second candidate uplink carriers from a set of candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0345] In some aspects, to support the transmission of second information, message manager 1745 is capable of, configured to, or operable to support components for transmitting broadcast or private messages including second information, wherein the second information indicates at least one of the following: frequency information of each of one or more second uplink carriers, uplink bandwidth portion information of each of one or more second uplink carriers, or timer information relating to time alignment of each of one or more second uplink carriers. In some aspects, the second information includes criteria for determining a first candidate uplink carrier by a second network node.

[0346] In some aspects, the standard includes a first received power threshold, and wherein a first uplink carrier or one of one or more second uplink carriers is determined as a first candidate uplink carrier based on a first comparison of the received power value with the first received power threshold.

[0347] In some aspects, the standard includes one or more second receive power thresholds and an association between each of the one or more second uplink carriers and a corresponding receive power value range, each corresponding receive power value range being defined by at least one of the one or more second receive power thresholds.

[0348] In some respects, determining a first candidate uplink carrier from one or more second uplink carriers is based on a second comparison of a received power value with one or more second received power thresholds.

[0349] In some respects, in order to support participation in a random access procedure, the random access manager 1735 is capable of, can be configured of, or is operable to support components for participating in a random access procedure using a first candidate uplink carrier and a first downlink carrier, wherein one of one or more second uplink carriers is the first candidate uplink carrier.

[0350] In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for receiving random access messages via a first candidate uplink carrier. In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for transmitting a random access response message via a first downlink carrier, wherein the random access response message is scheduled for transmission of an uplink shared channel message via the first candidate uplink carrier. In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for receiving uplink shared channel messages via the first candidate uplink carrier based on random access response messages. In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for transmitting contention-solving downlink messages for the contention-solving procedure via the first downlink carrier based on uplink shared channel messages.

[0351] In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for receiving random access messages via a first candidate uplink carrier. In some aspects, to support participation in the random access procedure, the random access manager 1735 can be, configured, or operated to support components for transmitting downlink messages based on random access messages via a first downlink carrier.

[0352] In some respects, a second uplink carrier is determined as a first candidate uplink carrier for the random access procedure based on one or more second uplink carriers, and at least the first uplink carrier is determined as a second candidate uplink carrier.

[0353] In some aspects, the feedback manager 1750 is capable of, configured to, or operable to support components for receiving feedback messages via a first uplink carrier in response to the end of a random access procedure. In some aspects, the uplink transmission manager 1740 is capable of, configured to, or operable to support components for receiving uplink transmissions via at least a first uplink carrier.

[0354] In some aspects, the feedback manager 1750 is capable of, configured to, or operable to support components for receiving feedback messages via a first candidate uplink carrier in response to the end of a random access procedure. In some aspects, the uplink transmission manager 1740 is capable of, configured to, or operable to support components for receiving uplink transmissions via at least a first candidate uplink carrier.

[0355] In some respects, the CIF manager 1755 is capable of, configured to, or operable to support components for receiving the group of multiple uplink transmissions via at least a first uplink carrier, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on the first downlink carrier is the same as a second value of a second carrier information field for scheduling uplink transmissions via one uplink of the first uplink carrier in the group of multiple uplink transmissions, and wherein the first value is different from a third value of a third carrier information field for scheduling uplink transmissions via another uplink of one or more second uplink carriers in the group of multiple uplink transmissions.

[0356] In some respects, a second uplink carrier is determined as a first candidate uplink carrier for the random access procedure based on one or more second uplink carriers, and at least that one of the one or more second uplink carriers is determined as a second candidate uplink carrier.

[0357] In some respects, the CIF manager 1755 is capable of, configured to, or operable to support components for receiving the group of multiple uplink transmissions via one of the one or more second uplink carriers, wherein a first value of a first carrier information field for scheduling downlink shared channel messages on a first downlink carrier is different from a second value of a second carrier information field for scheduling uplink transmissions via one of the one or more second uplink carriers in the group of multiple uplink transmissions, and wherein the first value is different from a third value of a third carrier information field for scheduling uplink transmissions via another of the one or more second uplink carriers in the group of multiple uplink transmissions.

[0358] In some aspects, the feedback manager 1750 is capable of, configured to, or operable to support components for receiving a feedback message via one of the one or more second uplink carriers in response to the end of a random access procedure. In some aspects, the uplink transmission manager 1740 is capable of, configured to, or operable to support components for receiving the uplink transmission via at least one of the one or more second uplink carriers.

[0359] In some aspects, uplink transmission includes one or more of uplink control channel messages, uplink shared channel messages, or random access channel messages. In some aspects, the second candidate uplink carrier is an uplink component carrier used for CA when the second network node is in connected mode.

[0360] In some respects, the second candidate uplink carrier is associated with a corresponding set of feedback procedures. In some respects, the combination of one or more second candidate uplink carriers, including the second candidate uplink carrier, is based on the capabilities of the second network node.

[0361] In some respects, the second candidate uplink carrier is scheduled based on downlink messages associated with the same cell. In other respects, half-duplex or full-duplex operation between the first downlink carrier and the second candidate uplink carrier is based on the capabilities of the second network node.

[0362] In some aspects, the first uplink carrier and one or more second uplink carriers are in different frequency bands. In other aspects, the first uplink carrier and one or more second uplink carriers are in the same frequency band.

[0363] In some aspects, the first uplink carrier and one or more second uplink carriers are used for communication between the second network node and different cells. In other aspects, the first uplink carrier and one or more second uplink carriers are used for communication between the second network node and the same cell.

[0364] In some respects, idle mode and connected mode are communication states of a first network node relative to a second network node, wherein communication during connected mode is allocated for resources used by the second network node, and wherein communication during idle mode is allocated for resources used by the common network node.

[0365] Figure 18 A block diagram 1800 of a device 1805 supporting signaling capabilities for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure, is shown. Device 1805 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1805 may include receiver 1810, transmitter 1815, and communication manager 1820. Device 1805 or one or more components of device 1805 (e.g., receiver 1810, transmitter 1815, and communication manager 1820) may also include at least one communication interface and at least one processor coupled to the communication interface to support the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0366] Receiver 1810 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1805. In some aspects, receiver 1810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0367] Transmitter 1815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1805. For example, transmitter 1815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some aspects, transmitter 1815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some aspects, transmitter 1815 and receiver 1810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0368] Device 1805 or its various components may be examples of parts used to perform various aspects of capability signaling for downlink and uplink carriers and cells in different frequency bands as described herein. For example, communication manager 1820 may include capability information manager 1825, carrier information manager 1830, wireless communication manager 1835, or any combination thereof. Communication manager 1820 may be examples of aspects of communication manager 1720 as described herein. In some aspects, communication manager 1820 or its various components may be configured to use or otherwise cooperate with receiver 1810, transmitter 1815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1820 may receive information from receiver 1810, transmit information to transmitter 1815, or be integrated in combination with receiver 1810, transmitter 1815, or both to acquire information, output information, or perform various other operations as described herein.

[0369] Capability information manager 1825 is capable of, configured to, or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Carrier information manager 1830 is capable of, configured to, or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the second network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, and wherein the carrier information is based on the capability information. Wireless communication manager 1835 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0370] Capability information manager 1825 is capable of, configured to, or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. Carrier information manager 1830 is capable of, configured to, or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by a first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. Wireless communication manager 1835 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on the carrier information.

[0371] Figure 19A block diagram 1900 illustrates a communication manager 1920 supporting capability signaling for downlink and uplink carriers and cells in different frequency bands, according to one or more aspects of this disclosure. The communication manager 1920 may be an example of aspects of the communication manager 1720, communication manager 1820, or both as described herein. The communication manager 1920 or its various components may be examples of parts for performing various aspects of capability signaling for downlink and uplink carriers and cells in different frequency bands as described herein. For example, the communication manager 1920 may include a capability information manager 1925, a carrier information manager 1930, a wireless communication manager 1935, a resource manager 1940, a random access manager 1945, an uplink transmission manager 1950, or any combination thereof. Each of these components, or components of their sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). This communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0372] Capability information manager 1925 is capable of, configured to, or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Carrier information manager 1930 is capable of, configured to, or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the second network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, and wherein the carrier information is based on the capability information. Wireless communication manager 1935 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0373] In some aspects, the capability information includes a first indication that the second network node supports communication in the first frequency band and a second indication that the second network node supports communication in the second frequency band. In some aspects, the capability of the second network node to communicate using the carrier is indicated by the first and second indications.

[0374] In some aspects, the capability information includes: a first list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of these individual frequency bands; and a second list of frequency band pairs, wherein for each pair, the second network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with that downlink communication via a second pair of components in the corresponding pair. In some aspects, the first frequency band and the second frequency band are one of the frequency band pairs included in the second list.

[0375] In some aspects, the capability information indicates one or more first group features and one or more second group features supported by the second network node. In some aspects, a single group of one or more first group features is associated with a corresponding downlink frequency band in a second list of frequency band pairs. In some aspects, a single group of one or more second group features is associated with a corresponding uplink frequency band in a second list of frequency band pairs. In some aspects, the capability information indicates one or more first group features and one or more second group features that are separate from a third group of features supported by the second network node and each associated with a corresponding individual frequency band from the first list.

[0376] In some aspects, the capability information includes a list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of these individual frequency bands. In some aspects, the list includes an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list of individual frequency bands. In some aspects, the second frequency band is included in an additional set of uplink frequency bands within the additional set of uplink frequency bands, where the corresponding individual frequency band belonging to that additional set of uplink frequency bands is the first frequency band.

[0377] In some aspects, the capability information indicates one or more first sets of features supported by the second network node and each associated with a corresponding individual frequency band from the list. In some aspects, the capability information also indicates one or more second sets of features supported by the second network node and each associated with at least one uplink frequency band from a corresponding set in an additional set of uplink frequency bands.

[0378] In some respects, the first frequency band is the TDD band. In other respects, the second frequency band is the FDD band or the SUL band.

[0379] In some respects, one or more downlink carriers include SDL carriers. In some respects, the first frequency band is an SDL frequency band that includes SDL carriers.

[0380] In some aspects, to support the transmission of carrier information, the resource manager 1940 is capable of, configured to, or operable to support components for transmitting first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier. In some aspects, to support the transmission of carrier information, the resource manager 1940 is capable of, configured to, or operable to support components for transmitting second information indicating a second resource for a first network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a group of multiple candidate uplink carriers.

[0381] In some aspects, to support participation in wireless communication, the random access manager 1945 is capable of, configured to, or operable to support components for participating in a random access procedure with a second network node using a first candidate uplink carrier from a set of multiple candidate uplink carriers. In some aspects, to support participation in wireless communication, the uplink transmission manager 1950 is capable of, configured to, or operable to support components for receiving uplink transmissions via a second candidate uplink carrier from a set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0382] In some respects, idle mode and connected mode are communication states of the second network node relative to the first network node. In some respects, communication during connected mode is for resources allocated for use by the second network node. In some respects, communication during idle mode is for resources allocated for use by the shared network node.

[0383] In some aspects, the capability information manager 1925 is capable of, configured to, or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. In some aspects, the carrier information manager 1930 is capable of, configured to, or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by a first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. In some aspects, the wireless communication manager 1935 is capable of, configured to, or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier according to the carrier information.

[0384] In some aspects, the capability information includes a first indication that the first network node supports communication in a first frequency band and a second indication that the first network node supports communication in a second frequency band. In some aspects, the capability of the first network node to communicate using the carrier pair is indicated by the first and second indications.

[0385] In some respects, the second uplink carrier is a SUL carrier when the second network node is in idle mode, and an uplink component carrier for CA when the second network node is in connected mode.

[0386] In some aspects, to support receiving carrier information, the resource manager 1940 is capable of, configured to, or operable to support components for transmitting first information indicating a first resource for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier. In some aspects, to support receiving carrier information, the resource manager 1940 is capable of, configured to, or operable to support components for transmitting second information indicating a second resource for a second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a group of multiple candidate uplink carriers.

[0387] In some aspects, to support participation in wireless communication, the random access manager 1945 is capable of, configured to, or operable to support components for participating in a random access procedure with a second network node using a first candidate uplink carrier from a set of multiple candidate uplink carriers. In some aspects, to support participation in wireless communication, the uplink transmission manager 1950 is capable of, configured to, or operable to support components for receiving uplink transmissions via a second candidate uplink carrier from a set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0388] In some respects, idle mode and connected mode are communication states of the second network node relative to the first network node. In some respects, communication during connected mode is on resources allocated for use by the second network node. In some respects, communication during idle mode is on resources allocated for use by the shared network node. In some respects, the first frequency band is a TDD frequency band.

[0389] Figure 20 A diagram of a system 2000 is shown, comprising a device 2005 supporting capability signaling for downlink and uplink carriers and cells in different frequency bands and also supporting a framework (e.g., an eSUL framework) for SUL and uplink CA, according to one or more aspects of this disclosure. Device 2005 may be an example of device 1505, device 1605, or network entity 105 as described herein, or may include components thereof. Device 2005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, the communication including communication via one or more wired interfaces, one or more radio interfaces, or any combination thereof. Device 2005 may include components supporting output and acquisition of communication, such as a communication manager 2020, transceiver 2010, antenna 2015, memory 2025, code 2030, and processor 2035. These components may communicate electronically via one or more buses (e.g., bus 2040) or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0390] Transceiver 2010 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some aspects, transceiver 2010 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some aspects, transceiver 2010 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some aspects, device 2005 may include one or more antennas 2015 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 2010 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 2015, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 2015, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 2010 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 2015 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 2015 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 2010 may include one or more processor or memory components or be configured to couple to said one or more processor or memory components, said one or more processor or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 2010, or transceiver 2010 and one or more antennas 2015, or transceiver 2010 and one or more antennas 2015 and one or more processor or memory components (e.g., processor 2035 or memory 2025 or both), may be included in a chip or chip assembly mounted in device 2005. In some respects, the transceiver may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0391] Memory 2025 may include RAM and ROM. Memory 2025 may store computer-readable, computer-executable code 2030, including instructions that, when executed by processor 2035, cause device 2005 to perform the various functions described herein. Code 2030 may be stored in a non-transitory computer-readable medium, such as system memory, or another type of memory. In some cases, code 2030 may not be directly executable by processor 2035, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 2025 may also contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0392] Processor 2035 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, processor 2035 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 2035. Processor 2035 may be configured to execute computer-readable instructions stored in memory (e.g., memory 2025) to cause device 2005 to perform various functions (e.g., functions or tasks supporting frameworks for SUL and uplink CA, and capability signaling for downlink and uplink carriers and cells in different frequency bands). For example, device 2005 or components thereof may include processor 2035 and memory 2025 coupled to processor 2035, wherein processor 2035 and memory 2025 are configured to perform the various functions described herein. Processor 2035 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions for performing the functions of device 2005 (e.g., by executing code 2030). Processor 2035 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 2005 (such as within memory 2025). In some specific implementations, processor 2035 may be a component of a processing system. A processing system can generally refer to a system or series of machines or components that receive input and process that input to produce a set of outputs that can be passed to, for example, other systems or components of device 2005. For example, a processing system of device 2005 may refer to a system that includes various other components or sub-components of device 2005 (such as processor 2035, or transceiver 2010, or communication manager 2020, or other components or combinations of components of device 2005). The processing system of device 2005 can interface with other components of device 2005 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 2005 may include a processing system and one or more interfaces for outputting information or for receiving information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, and other specific implementations. In some specific implementations, the one or more interfaces may refer to the interface between the processing system of the chip or modem and a transmitter, enabling device 2005 to transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, the one or more interfaces may refer to the interface between the processing system of a chip or modem and the receiver, enabling the device 2005 to receive information or signal input, and such information to be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0393] In some aspects, bus 2040 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some aspects, bus 2040 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 2005, or communication performed between different components of device 2005 that may be co-located or located in different locations (e.g., where device 2005 may refer to a system in which one or more of communication manager 2020, transceiver 2010, memory 2025, code 2030, and processor 2035 may be located in one of the different components or partitioned between the different components).

[0394] In some aspects, the Communication Manager 2020 can manage various aspects of communication with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the Communication Manager 2020 can manage the delivery of data communications by client devices (such as one or more UEs 115). In some aspects, the Communication Manager 2020 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UE 115. In some aspects, the Communication Manager 2020 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0395] For example, the communication manager 2020 can be configured or operable to support components for transmitting first information indicating a first resource for a second network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. The communication manager 2020 can be configured or operable to support components for transmitting second information indicating a second resource for a second network node to communicate via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively form a set of multiple candidate uplink carriers. The communication manager 2020 can be configured or operable to support components for participating in a random access procedure with the second network node using a first candidate uplink carrier from a set of multiple candidate uplink carriers. The communication manager 2020 can be configured or operable to support components for receiving uplink transmissions via second candidate uplink carriers from a set of multiple candidate uplink carriers after the random access procedure and when the second network node is in connected mode.

[0396] For example, the communication manager 1420 can be configured or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. The communication manager 1420 can be configured or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by the second network node, wherein the one or more downlink carriers include a first downlink carrier and the one or more uplink carriers include a first uplink carrier, wherein the carrier information is based on the capability information. The communication manager 1420 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the first uplink carrier based on the carrier information.

[0397] For example, the communication manager 1420 can be configured or operable to support components for receiving capability information indicating the capability of a second network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band. The communication manager 1420 can be configured or operable to support components for transmitting carrier information indicating one or more downlink carriers and one or more uplink carriers for wireless communication by a first network node, wherein the one or more downlink carriers include a first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band. The communication manager 1420 can be configured or operable to support components for participating in wireless communication via the first downlink carrier and the second uplink carrier based on the carrier information.

[0398] By including or configuring a communication manager 2020 according to an example as described herein, device 2005 can support a unified framework for SUL and uplink CA, as well as signaling capabilities for uplink and downlink carriers in different frequency bands. These technologies can reduce latency, improve spectrum efficiency, improve resource utilization efficiency, increase signaling capacity, and improve communication between network nodes.

[0399] In some aspects, the communication manager 2020 may be configured to use or otherwise coordinate with the transceiver 2010, one or more antennas 2015 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 2020 is exemplified as a separate component, in some aspects, one or more functions described with reference to the communication manager 2020 may be supported or performed by the transceiver 2010, processor 2035, memory 2025, code 2030, or any combination thereof. For example, code 2030 may include instructions that can be executed by the processor 2035 to cause the device 2005 to perform various aspects of the framework for SUL and uplink CA as described herein, as well as the capability signaling for downlink and uplink carriers and cells in different frequency bands, or the processor 2035 and memory 2025 may be otherwise configured to perform or support such operations.

[0400] Figure 21A flowchart illustrating method 2100, which exemplifies various aspects of this disclosure, supports a framework (e.g., an eSUL framework) for SUL and uplink CA. Operation of method 2100 can be implemented by a UE or its components as described herein. For example, operation of method 2100 can be achieved by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some aspects, the UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally or alternatively, the wireless UE may use dedicated hardware to perform aspects of the described functions.

[0401] At 2105, the method may include receiving first information indicating a first resource for a first network node to communicate via at least one of a first uplink carrier and a first downlink carrier paired with the first uplink carrier in the same frequency band. Operation of 2105 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 2105 may be provided by reference to... Figure 10 The described carrier pair is executed by component 1025.

[0402] At 2110, the method may include receiving second information indicating second resources for a first network node to communicate via one or more second uplink carriers associated with a first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers collectively constitute a set of multiple candidate uplink carriers. Operation of 2110 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 2110 may be provided by reference to... Figure 10 The SUL carrier component 1030 described is implemented.

[0403] At 2115, the method may include determining a first candidate uplink carrier for the random access procedure from a set of multiple candidate uplink carriers when the first network node is in an idle mode. The operation of 2115 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 2115 may be derived from references... Figure 10 The described random access component 1035 is executed.

[0404] At 2120, the method may include determining a second candidate uplink carrier from a plurality of candidate uplink carriers for uplink transmission when the first network node is in connected mode. The operation of 2120 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 2120 may be derived from references... Figure 10 The described uplink component 1040 is executed.

[0405] Figure 22A flowchart illustrating method 2200, which exemplifies various aspects of this disclosure, supports a framework (e.g., an eSUL framework) for SUL and uplink CA. Operation of method 2200 can be implemented by a UE or its components as described herein. For example, operation of method 2200 can be achieved by, as referenced... Figures 1 to 14 The UE 115 described herein pe...

Claims

1. A first network node for wireless communication, the first network node comprising: At least one communication interface; and At least one processor, coupled to the communication interface, wherein the first network node is configured to: Send capability information, which indicates the first network node’s ability to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in the first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Receive carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; as well as Based on the carrier information, the wireless communication is conducted via the first downlink carrier and the first uplink carrier.

2. The first network node according to claim 1, wherein the capability information includes a first indication that the first network node supports communication in the first frequency band and a second indication that the first network node supports communication in the second frequency band, the capability of the first network node to communicate using the pair of carriers being indicated by the first indication and the second indication.

3. The first network node according to claim 1, wherein the capability information includes: A first list of individual frequency bands, wherein the first network node supports both downlink and uplink communication via each of the individual frequency bands; The second list of frequency band pairs, wherein for each pair, the first network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with the downlink communication via a second pair of components in the corresponding pair, wherein the first frequency band and the second frequency band are one of the frequency band pairs included in the second list.

4. The first network node of claim 3, wherein the capability information indicates one or more first sets of features supported by the first network node and one or more second sets of features supported by the first network node, wherein a single set of the one or more first sets of features is associated with a corresponding downlink frequency band in a second list of the frequency band pair, and a single set of the one or more second sets of features is associated with a corresponding uplink frequency band in a second list of the frequency band pair, wherein the capability information indicates the one or more first sets of features and the one or more second sets of features that are separate from a third set of features supported by the first network node and each associated with a corresponding single frequency band from the first list.

5. The first network node of claim 1, wherein the capability information comprises a list of individual frequency bands, wherein the first network node supports both downlink and uplink communication via each of the individual frequency bands, and the list comprises an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list of individual frequency bands, the second frequency band being included in an additional set of uplink frequency bands in the additional set of uplink frequency bands, wherein the corresponding individual frequency band belonging to the additional set of uplink frequency bands is the first frequency band.

6. The first network node of claim 5, wherein the capability information indicates one or more first sets of features supported by the first network node and each associated with a corresponding individual frequency band from the list, and the capability information further indicates one or more second sets of features supported by the first network node and each associated with at least one uplink frequency band from a corresponding set in the additional set of uplink frequency bands.

7. The first network node according to claim 1, wherein the first frequency band is a time-division duplex frequency band, and the second frequency band is a frequency-division duplex frequency band or a supplementary uplink frequency band.

8. The first network node of claim 1, wherein the one or more downlink carriers include supplementary downlink carriers, and the first frequency band is a supplementary downlink frequency band including the supplementary downlink carriers.

9. A first network node for wireless communication, the first network node comprising: At least one communication interface; and At least one processor, coupled to the communication interface, wherein the first network node is configured to: Send capability information, which indicates the ability of the first network node to communicate using a pair of carriers in the same frequency band, wherein the pair of carriers includes a first downlink carrier and a first uplink carrier in the first frequency band; Receive carrier information indicating one or more downlink carriers and one or more uplink carriers for the first network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier, and the one or more uplink carriers include the first uplink carrier and a second uplink carrier in the first frequency band, wherein the carrier information includes second carrier information based on the capability information and based on the first uplink carrier and the second uplink carrier being in the same frequency band; as well as Based on the carrier information, the wireless communication is conducted via the first downlink carrier and the second uplink carrier.

10. The first network node of claim 9, wherein the capability information includes a first indication that the first network node supports communication in the first frequency band and a second indication that the first network node supports communication in the second frequency band, the capability of the first network node to communicate using the pair of carriers being indicated by the first indication and the second indication.

11. The first network node according to claim 9, wherein the second uplink carrier is a supplementary uplink carrier when the first network node is in idle mode, and is an uplink component carrier for carrier aggregation when the first network node is in connected mode.

12. The first network node according to claim 9, wherein the first frequency band is a time-division duplex frequency band.

13. A first network node for wireless communication, the first network node comprising: At least one communication interface; and At least one processor, coupled to the communication interface, wherein the first network node is configured to: The capability information indicates the ability of the second network node to communicate using a pair of carriers in different frequency bands, wherein the pair of carriers includes a first downlink carrier in a first frequency band and a first uplink carrier in a second frequency band different from the first frequency band. Send carrier information for one or more downlink carriers and one or more uplink carriers for the second network node to use for wireless communication, wherein the one or more downlink carriers include the first downlink carrier and the one or more uplink carriers include the first uplink carrier, wherein the carrier information is based on the capability information; as well as Based on the carrier information, the wireless communication is conducted via the first downlink carrier and the first uplink carrier.

14. The first network node of claim 13, wherein the capability information includes a first indication that the second network node supports communication in the first frequency band and a second indication that the second network node supports communication in the second frequency band, the capability of the second network node to communicate using the pair of carriers being indicated by the first indication and the second indication.

15. The first network node according to claim 13, wherein the capability information includes: A first list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of the individual frequency bands; A second list of frequency band pairs, wherein for each pair, the second network node supports downlink communication via a first pair of components in the corresponding pair and uplink communication associated with the downlink communication via a second pair of components in the corresponding pair, wherein the first frequency band and the second frequency band are one of the frequency band pairs included in the second list.

16. The first network node of claim 15, wherein the capability information indicates one or more first sets of features supported by the second network node and one or more second sets of features supported by the second network node, wherein a single set of the one or more first sets of features is associated with a corresponding downlink frequency band in a second list of the frequency band pair, and a single set of the one or more second sets of features is associated with a corresponding uplink frequency band in a second list of the frequency band pair, wherein the capability information indicates the one or more first sets of features and the one or more second sets of features separate from a third set of features supported by the second network node and each associated with a corresponding single frequency band from the first list.

17. The first network node of claim 13, wherein the capability information comprises a list of individual frequency bands, wherein the second network node supports both downlink and uplink communication via each of the individual frequency bands, and the list comprises an additional set of uplink frequency bands, each set of uplink frequency bands being associated with a corresponding individual frequency band in the list of individual frequency bands, the second frequency band being included in an additional set of uplink frequency bands in the additional set of uplink frequency bands, the corresponding individual frequency band belonging to the additional set of uplink frequency bands being the first frequency band.

18. The first network node of claim 17, wherein the capability information indicates one or more first sets of features supported by the second network node and each associated with a corresponding individual frequency band from the list, and the capability information further indicates one or more second sets of features supported by the second network node and each associated with at least one uplink frequency band from a corresponding set in the additional set of uplink frequency bands.

19. The first network node according to claim 13, wherein the first frequency band is a time-division duplex frequency band, and the second frequency band is a frequency-division duplex frequency band or a supplementary uplink frequency band.

20. The first network node of claim 13, wherein the one or more downlink carriers include supplementary downlink carriers, and the first frequency band is a supplementary downlink frequency band including the supplementary downlink carriers.

21. A first network node for wireless communication, the first network node comprising: Memory; and At least one processor, coupled to the memory, wherein the at least one processor is configured to: Receive first information indicating a first resource for the first network node to communicate via at least one of a first uplink carrier and a first downlink carrier in the same frequency band paired with the first uplink carrier; The first network node receives second information indicating second resources for communicating via one or more second uplink carriers associated with the first downlink carrier but different from the first uplink carrier, wherein the first uplink carrier and the one or more second uplink carriers are collectively a plurality of candidate uplink carriers. When the first network node is in idle mode, a first candidate uplink carrier for the random access procedure is determined from the plurality of candidate uplink carriers; as well as When the first network node is in connected mode, a second candidate uplink carrier for uplink transmission is determined from the plurality of candidate uplink carriers.

22. The first network node of claim 21, wherein, in order to receive the second information, the at least one processor is configured to: Receive a broadcast or private message including the second information, wherein the second information indicates at least one of the following: frequency information of each of the one or more second uplink carriers, uplink bandwidth portion information of each of the one or more second uplink carriers, or timer information relating to time alignment of each of the one or more second uplink carriers.

23. The first network node of claim 21, wherein the second information includes criteria for determining the first candidate uplink carrier by the first network node.

24. The first network node of claim 23, wherein the criterion includes a first received power threshold, and wherein, in order to determine the first candidate uplink carrier, the at least one processor is configured to: Determine the received power value; and Based on a first comparison between the received power value and the first received power threshold, the first uplink carrier or one of the one or more second uplink carriers is determined as the first candidate uplink carrier.

25. The first network node of claim 24, wherein the criterion includes one or more second receive power thresholds and an association between each of the one or more second uplink carriers and a corresponding receive power value range, each corresponding receive power value range being defined by at least one of the one or more second receive power thresholds.

26. The first network node of claim 25, wherein the first candidate uplink carrier is determined from the one or more second uplink carriers based on a second comparison of the received power value with the one or more second received power thresholds.

27. The first network node of claim 21, wherein the at least one processor is configured to: The random access procedure is performed using the first candidate uplink carrier and the first downlink carrier, wherein one of the one or more second uplink carriers is the first candidate uplink carrier.

28. The first network node of claim 27, wherein, in order to perform the random access procedure, the at least one processor is configured to: A random access message is sent via the first candidate uplink carrier; For monitoring the downlink channel in response to a random access response message transmitted via the first downlink carrier, wherein the random access response message is scheduled to be transmitted via the uplink shared channel message of the first candidate uplink carrier; Based on the random access response message, the uplink shared channel message is transmitted via the first candidate uplink carrier; as well as Based on the uplink shared channel message, the downlink message is resolved by receiving contention via the first downlink carrier.

29. The first network node of claim 27, wherein, in order to perform the random access procedure, the at least one processor is configured to: Transmit random access messages via the first candidate uplink carrier; and Based on the random access message, the downlink channel is monitored for downlink messages transmitted via the first downlink carrier.

30. The first network node of claim 21, wherein, in order to determine the second candidate uplink carrier, the at least one processor is configured to: The first uplink carrier is determined as the second candidate uplink carrier, wherein the determination of the first uplink carrier is based on one of the one or more second uplink carriers being determined as the first candidate uplink carrier for the random access procedure.

Images