Carrier aggregation configuration in 5G wireless networks

Abstract

The radio access network element includes at least one processor and at least one memory having computer program code configured to cause, with the at least one processor, the radio access network element to: generate a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including, for each band in a band combination, at least maximum supported channel bandwidth information and minimum supported channel bandwidth information; and transmit the carrier aggregation configuration to the user equipment to configure the user equipment for communication with the radio access network element.

Description

[Technical Field]

[0001] One or more exemplary embodiments relate to wireless communication networks. [Background technology]

[0002] Fifth-generation (5G) wireless communication networks are the next generation of mobile communication networks. Standards for 5G communication networks are currently being developed by the 3rd Generation Partnership Project (3GPP). These standards are known as 3GPP New Radio (NR) standards. Summary of the Invention

[0003] The scope of protection sought for various exemplary embodiments is defined by the independent claims. The exemplary embodiments and / or features described herein that do not fall within the scope of the independent claims, if any, should be interpreted as examples that serve to understand the various embodiments.

[0004] One or more exemplary embodiments provide mechanisms that may reduce the need to add Bandwidth Combining Sets (BCS) and / or reduce the number of updates required for gNBs in Third Generation Partnership Project (3GPP) New Radio (NR) networks.

[0005] One or more exemplary embodiments may reduce the need to update existing NR CA BCS tables in the 3GPP Radio Access Network Working Group 4 (RAN4) specifications and / or reduce the need for gNBs to import these tables into software.

[0006] One or more exemplary embodiments may also reduce the need to report redundant information to the gNB, thereby reducing signaling overhead and / or improving bandwidth capacity.

[0007] At least one example embodiment provides a radio access network element including at least one processor and at least one memory having computer program code configured to cause, with the at least one processor, the radio access network element to: generate a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including, for each band in a band combination, at least maximum supported channel bandwidth information and minimum supported channel bandwidth information; and transmit the carrier aggregation configuration to the user equipment to configure the user equipment for communication with the radio access network element.

[0008] At least one other example embodiment provides a radio access network element including: means for generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for each band in a band combination; and means for transmitting the carrier aggregation configuration to the user equipment to configure the user equipment for communication with the radio access network element.

[0009] At least one other example embodiment provides a method that includes generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for each band in a band combination, and transmitting the carrier aggregation configuration to the user equipment to configure the user equipment for communication with a radio access network element.

[0010] At least one other example embodiment provides a non-transitory computer-readable medium storing computer-readable instructions that, when executed by at least one processor at a radio access network element, cause the radio access network element to perform a method including: generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for each band in a band combination; and transmitting the carrier aggregation configuration to the user equipment to configure the user equipment for communication with the radio access network element.

[0011] According to at least some example embodiments, the at least one memory and computer program code may be configured, using the at least one processor, to cause a radio access network element to generate a carrier aggregation configuration without storing a definition of each bandwidth combination set supported by the user equipment.

[0012] The maximum supported channel bandwidth information may include a maximum supported channel bandwidth per subcarrier spacing for each band in the band combination.

[0013] The supported minimum channel bandwidth information may include a supported minimum channel bandwidth per subcarrier spacing for each band in the band combination.

[0014] The user equipment may support a subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation, and the capability information may include an indication of the channel bandwidth in the subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation.

[0015] The at least one memory and computer program code may be configured, with the at least one processor, to cause a radio access network element to send a capability query requesting capability information from a user equipment.

[0016] The capability information may include an indication that the capability information includes information to identify the supported channel bandwidth for each band in the band combination.

[0017] The at least one memory and computer program code may be configured, using the at least one processor, to cause a radio access network element to transmit the carrier aggregation configuration to a user equipment as a radio resource control message.

[0018] The band combination may include at least a first new radio band and a second new radio band, the supported maximum channel bandwidth information may include (i) a first supported maximum channel bandwidth per subcarrier spacing for the first new radio band and (ii) a second supported maximum channel bandwidth per subcarrier spacing for the second new radio band, and the supported minimum channel bandwidth information may include (i) a first supported minimum channel bandwidth per subcarrier spacing for the first new radio band and (ii) a second supported minimum channel bandwidth per subcarrier spacing for the second new radio band. The carrier aggregation configuration may include a combination of the first supported channel bandwidth per subcarrier spacing for the first new radio band and the second supported channel bandwidth per subcarrier spacing for the second new radio band.

[0019] The capability information may include (i) an indication of a first supported channel bandwidth per subcarrier spacing for a first New Radio Band for single-band operation, and (ii) an indication of a second supported channel bandwidth per subcarrier spacing for a second New Radio Band for single-band operation.

[0020] At least one other example embodiment provides a user equipment including at least one processor and at least one memory having computer program code thereon, the at least one memory and the computer program code causing the at least one processor to generate, in the user equipment, capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for each band in a band combination, transmit the capability information to a radio access network element, and receive from the radio access network element a carrier aggregation configuration, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring the user equipment for communication with the radio access network element; The method is configured to cause the

[0021] At least one other example embodiment provides a user equipment including: means for generating, for each band in a band combination, capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information; means for transmitting the capability information to a radio access network element; and means for receiving a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring the user equipment for communication with the radio access network element.

[0022] At least one other example embodiment provides a method that includes generating, for each band in a band combination, capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information; transmitting the capability information to a radio access network element; and receiving a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring user equipment for communication with the radio access network element.

[0023] At least one other example embodiment provides a non-transitory computer-readable medium storing computer-readable instructions that, when executed by at least one processor at a user equipment, cause the user equipment to perform a method including: generating capability information, for each band in a band combination, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information; transmitting the capability information to a radio access network element; and receiving a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring the user equipment for communication with the radio access network element.

[0024] The capability information enables the radio access network element to generate a carrier aggregation configuration for the user equipment based on the capability information.

[0025] The maximum supported channel bandwidth information may include a maximum supported channel bandwidth per subcarrier spacing for each band in the band combination.

[0026] The supported minimum channel bandwidth information may include a supported minimum channel bandwidth per subcarrier spacing for each band in the band combination.

[0027] The user equipment may support a subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation, and the capability information may include an indication of the channel bandwidth in the subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation.

[0028] The at least one memory and computer program code may be configured, with the at least one processor, to cause the user equipment to generate capability information in response to a capability inquiry from a radio access network element.

[0029] The capability information may include an indication that the capability information includes information for the radio access network to identify supported channel bandwidths for each band in the band combination.

[0030] The at least one memory and computer program code can be configured, with the at least one processor, to cause the user equipment to transmit capability information to a radio access network element via radio resource control signaling.

[0031] The band combination may include at least a first New Radio band and a second New Radio band, the supported maximum channel bandwidth information includes (i) a first supported maximum channel bandwidth per subcarrier spacing for the first New Radio band and (ii) a second supported maximum channel bandwidth per subcarrier spacing for the second New Radio band, and the supported minimum channel bandwidth information includes (i) a first supported minimum channel bandwidth per subcarrier spacing for the first New Radio band and (ii) a second supported minimum channel bandwidth per subcarrier spacing for the second New Radio band. The carrier aggregation configuration may include a combination of the first supported channel bandwidth per subcarrier spacing for the first New Radio band and the second supported channel bandwidth per subcarrier spacing for the second New Radio band.

[0032] The capability information may include (i) an indication of a first supported channel bandwidth per subcarrier spacing for a first New Radio Band for single-band operation, and (ii) an indication of a second supported channel bandwidth per subcarrier spacing for a second New Radio Band for single-band operation.

[0033] Exemplary embodiments will become more fully understood from the detailed description given herein below and the accompanying drawings, in which like elements are represented by like reference numerals, and which are given by way of example only and therefore not to limit the present disclosure. [Brief explanation of the drawings]

[0034] [Figure 1] 1 shows a simplified diagram of a portion of a 3rd Generation Partnership Project (3GPP) New Radio (NR) access deployment to illustrate an example embodiment. [Figure 2]FIG. 1 is a signal flow diagram illustrating a method according to an exemplary embodiment. [Figure 3] 1 is a block diagram illustrating an exemplary embodiment of a UE. [Figure 4] 1 illustrates an example of a 3GPP Long Term Evolution (3GPP-LTE) CA bandwidth combination set (BCS) defined for inter-band (two-band) carrier aggregation (CA). [Figure 5] 1 shows an example of a 3GPP NR CA BCS defined for inter-band (two-band) CA. [Figure 6] 1 shows another example of a 3GPP NR CA BCS defined for inter-band (two-band) CA. DETAILED DESCRIPTION OF THE INVENTION

[0035] It should be noted that these figures are intended to illustrate general characteristics of methods, structures, and / or materials utilized in certain exemplary embodiments and to supplement the descriptions provided below. However, these figures are not to scale, may not accurately reflect the precise structural or performance characteristics of any given embodiment, and should not be construed as defining or limiting the range of values ​​or characteristics encompassed by the exemplary embodiments. The use of similar or identical reference numbers in various figures is intended to indicate the presence of similar or identical elements or features.

[0036] Various exemplary embodiments will now be described more fully with reference to the accompanying drawings, in which several exemplary embodiments are shown.

[0037] Detailed exemplary embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are merely representative for purposes of describing the exemplary embodiments. However, these exemplary embodiments may be embodied in many alternative forms and should not be construed as being limited to only the embodiments described herein.

[0038] It is to be understood that there is no intention to limit the example embodiments to the particular forms disclosed. On the contrary, the example embodiments are intended to cover all modifications, equivalents, and alternatives falling within the scope of this disclosure. Like numbers refer to like elements throughout the description of the figures.

[0039] While one or more exemplary embodiments may be described in terms of a radio access network (RAN) or radio network element (e.g., gNB), user equipment (UE), etc., it should be understood that one or more exemplary embodiments discussed herein may be executed by one or more processors (or processing circuitry) in a device to which the one or more exemplary embodiments are applicable. For example, according to one or more exemplary embodiments, at least one memory may include or store computer program code, and the at least one memory and computer program code may be configured, using the at least one processor, to cause the radio network element (or user equipment) to perform the operations discussed herein.

[0040] As discussed herein, the terms "one or more" and "at least one" can be used interchangeably.

[0041] As discussed herein, a gNB may also be referred to as a base station, access point, enhanced NodeB (eNodeB), or more generally, a radio access network element, radio network element, or network node. UEs may also be referred to herein as mobile stations and may include mobile phones, cell phones, smartphones, handsets, personal digital assistants (PDAs), tablets, laptop computers, phablets, etc.

[0042] It will be understood that several exemplary embodiments may be used in combination.

[0043] The 3rd Generation Partnership Project (3GPP) Radio Access Network (RAN) Working Group 4 (WG4(RAN4)) specifies supported bandwidth combination sets (BCS) for each band combination for 3GPP New Radio (NR) carrier aggregation (CA), multi-radio access technology (multi-RAT) dual connectivity (MR-DC), and 3GPP Long Term Evolution (LTE) CA. The benefit of a BCS is that it allows a UE to support channel bandwidth (CBW) combinations optimized (e.g., the minimum number) for a specific operator or region, potentially reducing costs by reducing the number of tests and interoperability development testing (IoDT) efforts.

[0044] However, specifying more than one BCS per band combination may increase the complexity of the RAN4 specification and / or may require (e.g., significant) additional standardization effort.

[0045] Figure 4 shows an example of 3GPP-LTE CA BCSs defined for inter-band CA. The example shown in Figure 4 includes LTE bands 4 and 12, and the maximum number of BCSs specified for one band combination is 6.

[0046] Figure 5 shows an example of a 3GPP NR CA BCS defined for inter-band CA. The example shown in Figure 5 includes BCSs BCS0 and BCS1 for bands n28 and n75.

[0047] Figure 6 shows another example of a 3GPP NR CA BCS defined for inter-band CA. More specifically, Figure 6 shows a hypothetical example of BCS2 for bands n28 and n75.

[0048] In operation, the UE reports the supported BCS(es) for each band combination to the base station via a UE capability report. Traditionally, the base station stores all utilized BCS(es) and supported CBW combinations for each band combination, interprets the reported UE capabilities, and ignores BCS(es) not utilized by the base station.

[0049] For 3GPP NR, the number of candidate CBWs is greater than the number of candidate CBWs for 3GPP LTE. Furthermore, as shown in FIG. 5, the supported CBWs according to the bands for 3GPP NR are different from the supported subcarrier spacing (SCS). As a result, the 3GPP NR BCS table is more complex than the 3GPP LTE BCS table. Furthermore, unlike 3GPP LTE, for 3GPP NR, new CBW(s) can be added to existing bands, which may require the introduction of new BCS(s). Therefore, the number of BCS(es) for an NR band combination may be greater than that for an LTE band combination. From a gNB implementation perspective, this situation may result in updating the gNB to store new BCS(es) more frequently than in a 3GPP LTE network.

[0050] The conventional method can realize the BCSs BCS0 and BCS1 in Figure 5. However, the conventional method cannot solve the case where the minimum CBW is limited to a portion (e.g., only a portion) of the 3GPP NR band within a BCS as shown in Figure 6, for example, because support of CBWs of 5, 10, and 15 MHz is mandatory for single-band operation in principle. While it is possible to not support the CBWs of 5, 10, and 15 MHz for each band within a band combination by not supporting these CBWs for single-band operation from a signaling perspective, this would result in these CBWs being unavailable even when CA is not required (e.g., during single-band operation), or would lead to a situation where a UE may not be able to use these CBWs on different networks around the world.

[0051] One or more exemplary embodiments introduce a signaling mechanism by which a UE can report the range of CBWs supported according to the SCS for each NR band in a band combination. In at least one exemplary embodiment, the UE can report the minimum CBW supported according to the SCS for each NR band in the band combination and the maximum CBW supported according to the SCS for each NR band in the band combination. One or more exemplary embodiments also provide a mechanism for the UE to indicate support for the exemplary embodiments discussed herein by transmitting a fixed BCS number, such as a BCS "x" (e.g., x=4) that is common to any or all band combinations, to the gNB.

[0052] More particularly, one or more example embodiments provide a mechanism for the UE to report the following parameters to the gNB, for example, by radio resource control (RRC) signaling: (i) The CBW(s) (if any) supported in accordance with the SCS for each NR band as single-band operation; (ii) the maximum CBW supported in accordance with the SCS for each NR band within the band combination; and (iii) The minimum CBW supported in accordance with the SCS for each NR band in the band combination.

[0053] The gNB, for the UE, identifies, based on at least parameters (ii) and (iii) above, supported CBW(s) according to the SCS for each NR band in the band combination, where the supported CBW combinations include each permutation of the supported CBWs according to the SCS for each NR band.

[0054] According to one or more exemplary embodiments, a BCS (e.g., BCS2) within NR may be implemented without explicitly adding a new BCS and without reporting the supported CBW(s) according to the SCS for each NR band for single-band operation. Thus, from the UE's perspective, selection of a CBW combination (e.g., an optimized one) may be possible to reduce costs. From the gNB's perspective, the gNB does not need to memorize (e.g., store) a definition of each BCS as in the prior art. Rather, the gNB can determine the supported CBW combination for a UE for a given band combination based on the capabilities reported by the UE. Capability reporting, and more generally, signaling between a UE and a gNB according to one or more exemplary embodiments, will be described in more detail below.

[0055] FIG. 1 shows a simplified diagram of a portion of a 3GPP NR access deployment to explain exemplary embodiments in more detail.

[0056] Referring to FIG. 1, a 3GPP NR radio access deployment includes a gNB 102 having transmit / receive points (TRPs) 102A, 102B, and 102C. Each TRP 102A, 102B, and 102C may be, for example, a remote radio head (RRH) or remote radio unit (RRU) including at least a radio frequency (RF) antenna (or antennas) or antenna panel and a radio transceiver for transmitting and receiving data within a geographic area. In this regard, the TRPs 102A, 102B, and 102C provide cellular resources to user equipment (UE) (e.g., UE 106) within a geographic coverage area. In some cases, baseband processing may be split between the TRPs 102A, 102B, and 102C within a fifth-generation (5G) cell and the gNB 102. Alternatively, baseband processing may be performed in the gNB 102. 1, the TRPs 102A, 102B, 102C are configured to communicate with the UE 106 via one or more transmit (TX) / receive (RX) beam pairs. The gNB 102 communicates with a core network, referred to as the New Core in 3GPP NR.

[0057] The TRPs 102A, 102B, and 102C may have independent schedulers, or the gNB 102 may perform joint scheduling among the TRPs 102A, 102B, and 102C.

[0058] Although only a single UE 106 is shown in Figure 1, the gNB 102 and TRPs 102A, 102B, 102C may provide communication services to a relatively large number of UEs within the coverage areas of the TRPs 102A, 102B, 102C. For clarity of the exemplary embodiments, communication services (including transmission and reception of wireless signals) are discussed as being between the gNB 102 and the UE 106. However, it should be understood that signals may be transmitted between the UE 106 and one or more of the TRPs 102A, 102B, 102C.

[0059] Exemplary functions and operations of the gNB 102 and the UE 106 in the context of RRC signaling are discussed in more detail below. Because RRC signaling is generally known, a detailed description will not be provided. Furthermore, although exemplary embodiments are discussed herein with respect to RRC signaling, the exemplary embodiments need not be limited to this example. Rather, other signaling mechanisms may be used.

[0060] FIG. 2 is a signal flow diagram illustrating a method according to an exemplary embodiment.

[0061] 2, at S202, the gNB 102 transmits a UE capability query (sometimes referred to herein as a UE capability request) to the UE 106, requesting capability information from the UE 106. In at least one example, the UE capability query may include a request for the UE 106 to report, among other things, BCS "x" (also referred to as BCSx) by including a given bit (or bit set) in a capability filter (e.g., transmitted to the gNB 102 by RRC signaling). The request may be, for example, capabilityRequestFilterCommon (including BCS "x"). The BCS "x" or BCSx may be a fixed BCS number, such as x=4, that is common to all band combinations and is used to inform the gNB 102 that the UE 106 supports one or more example embodiments described herein.

[0062] Assuming the UE 106 supports the mechanisms discussed herein, in S204, the UE 106 synthesizes a capability container (ue-CapabilityRAT-Container) based on the request to report BCS "x" and generates BCS information BCS_Info for the UE 106. In at least one example, the BCS information BCS_Info includes the following parameters for each SCS: CBWperBandperSCS: Supported CBW(s) per NR band for single-band operation (this parameter may be optional depending on whether there are any CBWs that meet this condition), supportedBandwidthDL: The maximum supported CBW per NR band in the band combination, and supportedMinBandwidthDL: The minimum supported CBW per NR band in the band combination.

[0063] The above parameters may be known (or alternatively (pre-)programmed) in the UE and / or based on the capabilities of the UE 106. Furthermore, the BCS information BCS_Info may be formatted according to the ASN.1 notation used in the RRC specification. Because such formats are known, a detailed description will be omitted.

[0064] 2, at S206, the UE 106 transmits the BCS information BCS_Info to the gNB 102. In at least one example, the UE 106 transmits the BCS information BCS_Info to the gNB 102 in a UE Capability Information RRC message. In one example, the UE Capability Information RRC message includes a capability container ue-CapabilityRAT-Container, which further includes the BCS information BCS_Info. The capability container CapabilityRAT-Container is listed in a capability container list UE-CapabilityRAT-ContainerList.

[0065] At S208, gNB102 receives BCS information BCS_Info from UE106 (e.g., included in a UE Capability Information RRC message) and records / stores the BCS information BCS_Info in the memory of gNB102.

[0066] At S210, the gNB 102 dynamically generates a CA configuration for the UE 106 based on the BCS information BCS_Info. The CA configuration may include one or more CBW(s) supported according to the SCS combination(s) of the identified band combination(s). More specifically, for example, at S210, the gNB 102 identifies, for each NR band in a given band combination, (i) the CBW(s) supported by the UE for each NR band as single-band operation, and (ii) the range of CBW(s) between the maximum supported CBW and the minimum supported CBW included in the BCS information BCS_Info from the UE 106. The gNB 102 then determines or identifies each combination of the CBW(s) supported according to the NR band as the CBW(s) supported according to the SCS combination(s) of the band combination(s). In one example, these combinations include all permutations of the CBW(s) supported according to the NR band. More specific examples of combinations of supported CBW(s) according to band will be discussed later.

[0067] According to one or more example embodiments, the gNB 102 does not need to store any tables associated with the BCS(es) in order to generate a CA configuration for the UE 106. Rather, the gNB 102 only needs to store the BCS information BCS_Info in order to generate the CA configuration on the fly (at runtime).

[0068] 2, after generating the CA configuration for the UE 106, the gNB 102 and the UE 106 exchange RRC (re)configuration messages at S212 and S214. RRC (re)configuration messages and their exchange between a gNB and a UE are generally known, so only a brief description is provided below.

[0069] More specifically, at S212, the gNB 102 sends an RRC (re)configuration message to the UE 106 including the determined CA configuration.

[0070] In response to the RRC (re)configuration message, the UE 106 performs CA configuration (not shown). Once complete, at S214, the UE 106 sends an RRC reconfiguration complete message to the gNB 102 indicating the same.

[0071] The UE 106 can then communicate with the gNB 102 on the downlink using the CA configuration provided by the gNB 102.

[0072] If there are any CBW(s) that are not supported for a given NR band, the UE 106 may explicitly report the CBW(s) that are supported by the UE 106. That is, for example, the UE 106 supports a subset of all channel bandwidths specified per subcarrier spacing for each band for single-band operation, and the UE 106 may provide an explicit indication of the channel bandwidths within the subset of all channel bandwidths specified per subcarrier spacing for each band for single-band operation.

[0073] However, from the perspective of the RAN2 specification, if all CBWs specified between 5, 10, 15, 20, 25, 30, 40, 50, 60, 80 and 100 MHz for the NR band between 410 MHz and 7125 MHz, or between 50, 100 and 200 MHz for the band between 24250 MHz and 52600 MHz, are supported by the UE, then the UE 106 does not actually need to explicitly report these CBWs to the gNB 102.

[0074] Although described with respect to downlink communications, the exemplary embodiments need not be limited to this example, but rather may also be applicable to uplink communications.

[0075] A more specific example is described below in which SCS=15 kHz and the band combination includes NR bands n28 and n75. However, it should be understood that exemplary embodiments need not be limited to this example. This example is described with reference to the signal flow diagram of FIG. 2 (where applicable) and the gNB 102 and UE 106 shown in FIG. 1.

[0076] In this example, the UE 106 may explicitly report the supported CBW(s) (e.g., 5, 10, 15, 20, and 30 MHz for NR band n28 and 5, 10, 15, 20, 25, 30, 40, and 50 MHz for NR band n75). However, as noted above, support for these CBWs is mandatory, so the UE 106 does not need to explicitly report these CBWs to the gNB 102.

[0077] In response to the UE capability query (S202), in S206, the UE 106 reports at least a supported maximum CBW for each NR band in the band combination using a single band entry and a single component carrier (CC) entry with a supported maximum CBW parameter supportedBandwidthDL, such that the supported maximum CBW parameter supportedBandwidthDL for NR band n28 is 20 MHz and the supported maximum CBW parameter supportedBandwidthDL for NR band n75 is 40 MHz. Also in S206, the UE 106 reports a supported minimum CBW for each NR band in the band combination using a single band entry and a single CC entry with a supported minimum CBW parameter supportedMinBandwidthDL, such that the supported minimum CBW parameter supportedMinBandwidthDL for NR band n28 is 10 MHz and the supported minimum CBW parameter supportedMinBandwidthDL for NR band n75 is 20 MHz. The UE 106 may also include (i) an indication of a first channel bandwidth supported per subcarrier spacing of the NR band n28 (first New Radio Band) for single-band operation, and (ii) an indication of a second channel bandwidth supported per subcarrier spacing of the NR band n75 (second New Radio Band) for single-band operation.

[0078] After storing the capability information reported from the UE 106 (S208), in S210, the gNB 102 determines that the supported CBW for the band combination is within a range between 10 MHz and 20 MHz (10 MHz≦CBW≦20 MHz) for NR band n28. Thus, in this example, the gNB 102 determines that the 10, 15, and 20 MHz bands are supported by the UE 106 for NR band n28. For NR band n75, the gNB 102 takes the reported information into account and determines that the supported CBW for the band combination is between 20 MHz and 40 MHz (20 MHz≦CBW≦40 MHz). Thus, the gNB 102 determines that the 20, 25, 30, and 40 MHz bands are supported for NR band n75.

[0079] Thus, in this example, the gNB 102 determines that the supported CBW(s) combination for the band combination are each combination of CBWs supported according to the NR band derived above. That is, in this example, for SCS = 15 kHz, the supported CBW combinations are (n28, n75) = (10,20), (10,25), (10,30), (10,40), (15,20), (15,25), ..., (20,40). Therefore, in this example, the unsupported CBW combinations (n28, n75) = (5,5), (5,10), and (5,15) can be omitted with relatively simple (less complex) signaling.

[0080] FIG. 3 illustrates an exemplary embodiment of the UE 106 shown in FIG.

[0081] As shown, the UE 106 includes a memory 740, a processor 720 connected to the memory 740, various interfaces 760 connected to the processor 720, and one or more (e.g., multiple) antennas or antenna panels 765 connected to the various interfaces 760. The various interfaces 760 and antennas 765 can comprise a transceiver for transmitting / receiving data, such as from / to the gNB 102 or from / to multiple TRPs 102A, 102B, 102C, over one or more wireless beams. As will be appreciated, depending on the implementation of the UE 106, the UE 106 can include more components than those shown in FIG. 3 . However, it is not necessary to show all of these typically conventional components to disclose an embodiment of the illustrative example.

[0082] Memory 740 may generally be a computer-readable storage medium including random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices such as a disk drive. Memory 740 also stores an operating system and any other routines / modules / applications to provide functionality of the UE 106 (e.g., UE functionality, methods according to exemplary embodiments, etc.) executed by processor 720. These software components may also be loaded into memory 740 from a separate computer-readable storage medium using a drive mechanism (not shown). Such separate computer-readable storage media may include a disk, tape, DVD / CD-ROM drive, memory card, or other similar computer-readable storage medium (not shown). In some exemplary embodiments, software components may be loaded into memory 740 through one of various interfaces 760 rather than through a computer-readable storage medium.

[0083] The processor 720 may be configured to execute computer program instructions by performing system arithmetic, logical, and input / output operations. These instructions may be provided to the processor 720 by the memory 740.

[0084] The various interfaces 760 may include components that interface the processor 720 with an antenna 765 or other input / output components. As will be appreciated, the various interfaces 760 and the programs stored in the memory 740 to define the dedicated functions of the UE 106 will vary depending on the implementation of the UE 106.

[0085] The interface 760 may also include one or more user input devices (eg, a keyboard, keypad, mouse, etc.) and user output devices (eg, a display, speaker, etc.).

[0086] 3 may be utilized to implement, among other things, the TRPs 102A, 102B, 102C, the gNB 102, and other radio access and backhaul network elements and / or devices. In this regard, for example, the memory 740 may store an operating system and any other routines / modules / applications (e.g., functions of these elements, methods according to example embodiments, etc.) to provide the functionality of the TRPs, gNBs, etc. executed by the processor 720.

[0087] Terms such as first, second, etc. may be used herein to describe various elements, but these elements are not necessarily limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the present disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0088] When an element is referred to as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be intervening elements. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements. Other language used to describe relationships between elements (e.g., "between" and "directly between," "adjacent" and "directly adjacent," etc.) should be construed in a similar manner.

[0089] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" are intended to encompass the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and / or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0090] It should also be noted that in some alternative implementations, the functions / acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may, in fact, be executed substantially in parallel, or may sometimes be executed in the reverse order, depending on the functions / acts involved.

[0091] Specific details are provided in the following description to provide a thorough understanding of the exemplary embodiments. However, it will be understood by those skilled in the art that the exemplary embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams in order to avoid obscuring the exemplary embodiments in unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the exemplary embodiments.

[0092] As discussed herein, exemplary embodiments are described with reference to acts and symbolic representations of operations (e.g., in the form of flowcharts, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.), which may be implemented as program modules or functional processes including routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types, and may be implemented using existing hardware in, for example, existing user equipment, base stations, eNBs, RRHs, gNBs, femto base stations, network controllers, computers, etc. Such existing hardware may be processing or control circuitry, such as, but not limited to, one or more processors, one or more central processing units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more systems-on-chips (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), or any other one or more devices capable of responding to and executing instructions in a defined manner.

[0093] Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel, concurrently, or simultaneously. Additionally, the order of operations may be rearranged. A process may terminate when its operations are completed, or may have additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or to the main function.

[0094] As disclosed herein, the terms "storage medium," "computer-readable storage medium," or "non-transitory computer-readable storage medium" can refer to one or more devices for storing data, including read-only memory (ROM), random-access memory (RAM), magnetic RAM, core memory, magnetic disk storage media, optical storage media, flash memory devices, and / or other tangible, machine-readable media for storing information. The term "computer-readable medium" can include, but is not limited to, portable or permanent storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instruction(s) and / or data.

[0095] Furthermore, the exemplary embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, program code or code segments to perform the necessary tasks may be stored on a machine or computer-readable medium, such as a computer-readable storage medium. When implemented in software, one or more processors perform the necessary tasks. For example, as described above, according to one or more exemplary embodiments, at least one memory may include or store computer program code, and the at least one memory and computer program code may be configured to cause at least one processor to perform the necessary tasks in a network element or network device. Furthermore, the processor, memory, and exemplary algorithms encoded as computer program code function as means for providing or causing the performance of the operations described herein.

[0096] A code segment of computer program code may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable technique including memory sharing, message passing, token passing, network transmission, etc.

[0097] As used herein, the terms "comprise" and / or "have" are defined as including (i.e., open language). As used herein, the term "coupled" is defined as connected, although not necessarily directly, and not necessarily mechanically. Terms derived from the word "pointing" (e.g., "point" and "indication") are intended to encompass all of the various techniques available for communicating or referencing the object / information being pointed to. Examples of techniques available for communicating or referencing the object / information being pointed to include: conveying the object / information being pointed to; conveying an identifier for the object / information being pointed to; conveying information used to generate the object / information being pointed to; conveying a part or portion of the object / information being pointed to; conveying some derivative of the object / information being pointed to; and conveying some symbol representing the object / information being pointed to.

[0098] According to example embodiments, user equipment, base stations, eNBs, RRHs, gNBs, femto base stations, network controllers, computers, etc. may be (or include) hardware, firmware, hardware executing software, or any combination thereof. Such hardware may include processing or control circuitry such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device or devices capable of responding to and executing instructions in a defined manner.

[0099] Although benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments of the present invention, the benefits, advantages, solutions to problems, and any element or elements that may provide or lead to such benefits, advantages, or solutions, or that may make such benefits, advantages, or solutions more noticeable, should not be construed as a critical, necessary, or essential feature or element of any or all of the claims.

Claims

1. at least one processor; at least one memory containing computer program code; A radio access network element comprising: The at least one memory and the computer program code are configured to cause the radio access network element, using the at least one processor, to: generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for at least one component carrier of each band in a band combination, the band combination including at least a first New Radio band and a second New Radio band; sending the carrier aggregation configuration to the user equipment based on the capability information to configure the user equipment for communication with the radio access network element; The radio access network element is configured to cause

2. The at least one memory and the computer program code are configured to cause the radio access network element, using the at least one processor, to:

2. The radio access network element of claim 1, configured to generate the carrier aggregation configuration without storing a definition of each bandwidth combination set supported by the user equipment.

3. the user equipment supports a subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation; 3. The radio access network element of claim 1, wherein the capability information includes an indication of channel bandwidths in a subset of all specified channel bandwidths for each subcarrier spacing for the single band operation.

4. The at least one memory and the computer program code are configured to cause the radio access network element, using the at least one processor, to: A radio access network element according to any one of claims 1 to 3, configured to cause the user equipment to send a capability query requesting said capability information.

5. 5. A radio access network element according to claim 1, wherein the capability information includes an indication that the capability information includes information for identifying supported channel bandwidths for each band in the band combination.

6. The at least one memory and the computer program code are configured to cause the radio access network element, using the at least one processor, to: A radio access network element according to any of claims 1 to 5, configured to cause the carrier aggregation configuration to be transmitted to the user equipment as a radio resource control message.

7. The supported maximum channel bandwidth information includes: (i) a first supported maximum channel bandwidth per subcarrier spacing for the first New Radio band; and (ii) a second supported maximum channel bandwidth per subcarrier spacing for the second New Radio band; the supported minimum channel bandwidth information includes: (i) a first supported minimum channel bandwidth per subcarrier spacing for the first New Radio band; and (ii) a second supported minimum channel bandwidth per subcarrier spacing for the second New Radio band; 7. The radio access network element according to claim 1, wherein the carrier aggregation configuration includes a combination of a first supported channel bandwidth per subcarrier spacing for the first New Radio band and a second supported channel bandwidth per subcarrier spacing for the second New Radio band.

8. generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for at least one component carrier of each band in a band combination, the band combination including at least a first New Radio band and a second New Radio band; sending the carrier aggregation configuration to the user equipment based on the capability information to configure the user equipment for communication with a radio access network element; A method comprising:

9. at least one processor; at least one memory containing computer program code; A user equipment including: The at least one memory and the computer program code are configured to, using the at least one processor, cause the user equipment to: generating capability information for the user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for at least one component carrier of each band in a band combination, wherein the band combination includes at least a first New Radio band and a second New Radio band; transmitting the capability information to a radio access network element; receiving a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring the user equipment for communication with the radio access network element; The user equipment is configured to cause

10. the user equipment supports a subset of all specified channel bandwidths per subcarrier spacing for each band for single-band operation; 10. The user equipment of claim 9, wherein the capability information includes an indication of a channel bandwidth in a subset of all the specified channel bandwidths for each subcarrier spacing for the single-band operation.

11. The at least one memory and the computer program code are configured to, using the at least one processor, cause the user equipment to: A user equipment according to any one of claims 9 to 10, configured to generate said capability information in response to a capability inquiry from said radio access network element.

12. 12. The user equipment of claim 9, wherein the capability information includes an indication that the capability information includes information for the radio access network element to identify supported channel bandwidths for each band in the band combination.

13. The at least one memory and the computer program code are configured to, using the at least one processor, cause the user equipment to: A user equipment according to any of claims 9 to 12, configured to cause said capability information to be transmitted to said radio access network element via radio resource control signalling.

14. The supported maximum channel bandwidth information includes: (i) a first supported maximum channel bandwidth per subcarrier spacing for the first New Radio band; and (ii) a second supported maximum channel bandwidth per subcarrier spacing for the second New Radio band; the supported minimum channel bandwidth information includes: (i) a first supported minimum channel bandwidth per subcarrier spacing for the first New Radio band; and (ii) a second supported minimum channel bandwidth per subcarrier spacing for the second New Radio band; The user equipment according to any one of claims 9 to 13, wherein the carrier aggregation configuration includes a combination of a first supported channel bandwidth per subcarrier spacing for the first New Radio band and a second supported channel bandwidth per subcarrier spacing for the second New Radio band.

15. generating capability information for a user equipment, the capability information including at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each subcarrier spacing for at least one component carrier of each band in a band combination, wherein the band combination includes at least a first New Radio band and a second New Radio band; transmitting the capability information to a radio access network element; receiving a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration based on the capability information, the carrier aggregation configuration configuring a user equipment for communication with the radio access network element; A method comprising:

Images