Network element, method and user equipment for carrier aggregation configuration

Abstract

A radio access network element includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause 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 at least a supported maximum channel bandwidth information and a supported minimum channel bandwidth information for each frequency band within a frequency band combination, and send the carrier aggregation configuration to the user equipment to configure the user equipment to communicate with the radio access network element.

Description

TECHNICAL FIELD

[0001] One or more example embodiments relate to wireless communication networks. BACKGROUND

[0002] Fifth generation (5G) wireless communication networks are next generation mobile communication networks. The Third Generation Partnership Project (3GPP) is currently developing standards for 5G communication networks. These standards are referred to as 3GPP New Radio (NR) standards. SUMMARY

[0003] The scope of protection sought for various example embodiments is set forth by the independent claims. The example embodiments and / or features described in this specification that are not within the scope of the independent claims (if any) should be interpreted as examples useful for understanding the example embodiments.

[0004] One or more example embodiments provide mechanisms that can alleviate the need to add a Bandwidth Combination Set (BCS) and / or reduce the number of updates required for a gNB in a Third Generation Partnership Project (3GPP) New Radio (NR) network.

[0005] One or more example embodiments can alleviate the need to update existing NR CA BCS tables in 3GPP Radio Access Network 4thWork Group (RAN4) specifications and / or can alleviate the need for a gNB to import these tables into software.

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

[0007] At least one example embodiment provides a radio access network element comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause 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 comprising at least maximum supported channel bandwidth information and minimum supported channel bandwidth information for each frequency band within a frequency band combination; and send the carrier aggregation configuration to the user equipment to configure the user equipment to communicate with the radio access network element.

[0008] At least one other example embodiment provides a user equipment comprising: means for sending capability information to a radio access network element, the capability information comprising at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each band within a band combination; and means for receiving a carrier aggregation configuration from the radio access network element based on the capability information.

[0009] At least one other example embodiment provides a method comprising: sending capability information to a radio access network element, the capability information comprising at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each band within a band combination; and receiving a carrier aggregation configuration from the radio access network element based on the capability information.

[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 user equipment, cause the user equipment to perform a method comprising: sending capability information to a radio access network element, the capability information comprising at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each band within a band combination; and receiving a carrier aggregation configuration from the radio access network element based on the capability information.

[0011] According to at least some example embodiments, the at least one memory and the computer program code can be configured to, with the at least one processor, cause the user equipment to receive the carrier aggregation configuration without storing a definition of each set of bandwidth combinations supported by the user equipment.

[0012] The supported maximum channel bandwidth information can comprise a supported maximum channel bandwidth for each subcarrier spacing of each band within the band combination.

[0013] The supported minimum channel bandwidth information can comprise a supported minimum channel bandwidth for each subcarrier spacing of each band within the band combination.

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

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

[0016] The capability information can include an indication that the capability information includes information identifying supported channel bandwidths for each frequency band within the frequency band combination.

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

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

[0019] The capability information can include (i) an indication of a first supported channel bandwidth for each subcarrier spacing for the first new radio frequency band as single-band operation, and (ii) an indication of a second supported channel bandwidth for each subcarrier spacing for the second new radio frequency band as single-band operation.

[0020] At least one other example embodiment provides a user equipment comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the user equipment to generate capability information including at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each frequency band within a frequency band combination, send the capability information to a radio access network element, and receive a carrier aggregation configuration from the radio access network element, the carrier aggregation configuration being based on the capability information and the carrier aggregation configuration configuring the user equipment to communicate with the radio access network element.

[0021] At least one other example embodiment provides a user equipment comprising means for generating capability information including at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each frequency band within a frequency band combination, means for sending 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 being based on the capability information and the carrier aggregation configuration configuring the user equipment to communicate with the radio access network element.

[0022] At least one other example embodiment provides a method comprising generating capability information including at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each frequency band within a frequency band combination, sending 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 being based on the capability information and the carrier aggregation configuration configuring the user equipment to communicate 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 comprising generating capability information including at least supported maximum channel bandwidth information and supported minimum channel bandwidth information for each subcarrier spacing of each frequency band within a frequency band combination, sending 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 being based on the capability information and the carrier aggregation configuration configuring the user equipment to communicate with the radio access network element.

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

[0025] The supported maximum channel bandwidth information can include a supported maximum channel bandwidth for each subcarrier spacing for each frequency band within the frequency band combination.

[0026] The supported minimum channel bandwidth information can include a supported minimum channel bandwidth for each subcarrier spacing for each frequency band within the frequency band combination.

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

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

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

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

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

[0032] The capability information can include (i) a first supported channel bandwidth for each subcarrier spacing of the first new radio frequency band as an indication of single band operation, and (ii) a second supported channel bandwidth for each subcarrier spacing of the second new radio frequency band as an indication of single band operation. BRIEF DESCRIPTION OF DRAWINGS

[0033] Example implementations will be more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numerals refer to like elements in which:

[0034] Figure 1 A simplified diagram showing a portion of a Third Generation Partnership Project (3GPP) New Radio (NR) access deployment for explaining example implementations is shown.

[0035] Figure 2 is a signal flow diagram illustrating a method according to example implementations.

[0036] Figure 3 is a block diagram illustrating an example implementation of a UE.

[0037] Figure 4 An example of a set of 3GPP Long Term Evolution (3GPP-LTE) Carrier Aggregation (CA) Bandwidth Combinations (BCS) defined for inter-band CA (two bands) is shown.

[0038] Figure 5 An example of a set of 3GPP NR CA BCS defined for inter-band CA (two bands) is shown.

[0039] Figure 6 Another example of a set of 3GPP NR CA BCS defined for inter-band CA (two bands) is shown.

[0040] It should be noted that these figures are intended to illustrate the general characteristics of methods, structures and / or materials utilized in certain example implementations, to supplement the written description provided below, and to complement the drawings. None of these drawings are necessarily drawn to scale, and are intended as illustrative only and not limiting of the scope of the example implementations in their definition or the scope of the values or properties they represent. Similar or identical reference numerals can be used in the various drawings to indicate like or similar components or features. DETAILED DESCRIPTION

[0041] Various example implementations will now be described more fully with reference to the accompanying drawings in which some example implementations are illustrated.

[0042] Detailed illustrative embodiments are disclosed herein. However, for the purposes of describing example embodiments, specific structural and functional details disclosed herein are representative only. Example embodiments can be embodied in many alternate forms and should not be construed as limited to the embodiments set forth herein.

[0043] It should be understood that the example embodiments are not intended to be limited to the particular forms disclosed. Instead, the example embodiments are to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure. Like numbers refer to like elements throughout the description of the figures.

[0044] When one or more example embodiments can be described from the perspective of a radio access network (RAN) or a radio network element (e.g., a gNB), a user equipment (UE), etc., it should be understood that one or more example embodiments discussed herein can be performed by one or more processors (or processing circuitry) at an applicable device. For example, according to one or more example embodiments, at least one memory can include or store computer program code, and the at least one memory and the computer program code can be configured to, together with at least one processor, cause a radio network element (or a user equipment) to perform operations discussed herein.

[0045] As discussed herein, the terms “one or more” and “at least one” can be used interchangeably.

[0046] As discussed herein, a gNB can also be referred to as a base station, an access point, an enhanced NodeB (eNodeB), or more generally as a radio access network element, a radio network element, or a network node. A UE can also be referred to as a mobile station herein and can include a mobile phone, a cellular phone, a smartphone, a handset, a personal digital assistant (PDA), a tablet computer, a laptop computer, a phablet, etc.

[0047] It should be appreciated that multiple example embodiments can be used in combination.

[0048] The 3rd Generation Partnership Project (3GPP) Radio Access Network (RAN) Working Group 4 (WG4 (RAN4)) has specified a set of supported bandwidth combinations (BCS) for each 3GPP New Radio (NR) Carrier Aggregation (CA), multi-RAT Dual Connectivity (MR-DC), and 3GPP Long Term Evolution (LTE) CA band combination. The advantage of a BCS is to allow a UE to support an optimized (e.g., minimum number of) channel bandwidth (CBW) combination for a particular operator or region, which can result in a reduction in cost due to less testing and interoperability development testing (IoDT) work.

[0049] However, specifying one or more BCS for each band combination may increase the complexity of the RAN4 specification and / or may require (e.g., a great deal) additional standardization work.

[0050] Figure 4 An example of 3GPP-LTE CA BCS for inter-band CA definition is shown. Figure 4 The examples shown include LTE bands 4 and 12, and the maximum number of designated BCSs for a band combination is six.

[0051] Figure 5 An example of 3GPP NR CA BCS defined for inter-band CA is shown. Figure 5 The examples shown include BCS BCS0 and BCS1 for frequency bands n28 and n75.

[0052] Figure 6 Another example of the 3GPP NR CA BCS defined for inter-band CA is shown. More specifically, Figure 6 An example of hypothetical BCS2 for frequency bands n28 and n75 is shown.

[0053] In operation, the UE reports the supported BCSs for each band combination to the base station via the UE Capability Report. Typically, the base station stores all the BCSs it utilizes and the supported CBW combinations for each band combination to interpret the reported UE capabilities, and ignores BCSs that are not utilized at the base station.

[0054] For 3GPP NR, the number of candidate CBWs is greater than that for 3GPP LTE. Additionally, as... Figure 5 As shown, each frequency band in 3GPP NR supports a different Carrier Component Warp (CBW) than the supported Subcarrier Spacing (SCS). Therefore, the 3GPP NR BCS table is more complex than the 3GPP LTE BCS table. Furthermore, unlike 3GPP LTE, new CBWs can be added to existing frequency bands for 3GPP NR, which may require the introduction of new BCSs. Therefore, the number of BCSs in an NR band combination may be greater than the number of BCSs in an LTE band combination. From the perspective of gNB implementation, this could lead to more frequent gNB updates to store new BCSs than in 3GPP LTE networks.

[0055] Conventional methods can achieve this Figure 5 The BCSs are BCS0 and BCS1. However, conventional methods cannot solve the problem where the minimum CBW is limited (e.g., only to) 3GPP NR bands in areas such as... Figure 6The case of some of the BCSs shown, because for example, support of 5, 10, and 15 MHz CBWs is mandatory for single-band operation in principle. Although it is possible that each band in a band combination does not support 5, 10, and 15 MHz CBWs, by not signaling these CBWs as single-band operation, this results in these CBWs being unavailable even when CA is not needed (e.g., in single-band operation), or in cases where the UE can not be able to use on different networks globally.

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

[0057] In more detail, one or more example embodiments provide a mechanism for a UE to report the following parameters to a gNB via, for example, radio resource control (RRC) signaling:

[0058] (i) supported CBWs for each SCS of each NR band as single-band operation (if any),

[0059] (ii) a maximum supported CBW for each SCS of each NR band within a band combination, and

[0060] (iii) a minimum supported CBW for each SCS of each NR band within a band combination.

[0061] The gNB identifies the supported CBWs for each SCS of each NR band within a band combination for the UE based on at least the above-discussed parameters (ii) and (iii). The supported CBW combination includes a permutation of each supported CBW for each SCS of each NR band.

[0062] According to one or more example embodiments, BCS in NR (e.g., BCS2) can be implemented without explicitly adding a new BCS and reporting each SCS for each NR band as a supported CBW for single-band operation. Thus, from a UE perspective, (e.g., optimized) CBW combination selection is possible for cost reduction. From a gNB perspective, the gNB does not need to memorize (e.g., store) the definition of each BCS as in conventional techniques. Rather, the gNB can determine the CBW combination that the UE supports for a given band combination based on the reported capability from the UE. Capability reporting and more generally signaling between a UE and a gNB according to one or more example embodiments will be discussed in more detail later.

[0063] Figure 1 A simplified diagram showing a portion of a 3GPP NR access deployment is shown for explaining example embodiments in more detail.

[0064] Reference Figure 1 The 3GPP NR radio access deployment includes a gNB 102 having transceiver points (TRPs) 102A, 102B, 102C. Each TRP 102A, 102B, 102C can be, for example, a remote radio head (RRH) or a remote radio unit (RRU) that includes at least, for example, a radio frequency (RF) antenna (or multiple antennas) or an antenna panel, and a radio transceiver for transmitting and receiving data within a geographic area. In this regard, the TRPs 102A, 102B, 102C provide cellular resources to user equipment (UE) (e.g., UE 106) within a geographic coverage area. In some cases, baseband processing can be distributed between the TRPs 102A, 102B, 102C and the gNB 102 in a 5thGeneration (5G) cell. Alternatively, baseband processing can be performed at the gNB 102. In some cases, the gNB 102 can be referred to as a base station, a NodeB, an eNodeB, a next generation eNodeB, or another similar term. Figure 1 In the example shown, 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 in 3GPP NR as a New Core.

[0065] The TRPs 102A, 102B, 102C can have independent schedulers, or the gNB 102 can perform joint scheduling between the TRPs 102A, 102B, 102C.

[0066] Although Figure 1Only a single UE 106 is shown, but the gNB 102 and the TRPs 102A, 102B, 102C can provide communication services to a relatively large number of UEs within the coverage areas of the TRPs 102A, 102B, 102C. For clarity of example embodiments, communication services (including transmission and reception of wireless signals) will be discussed between the gNB 102 and the UE 106. However, it should be understood that signals can be transmitted between the UE 106 and one or more of the TRPs 102A, 102B, 102C.

[0067] Example functions and operations of the gNB 102 and the UE 106 in the context of RRC signaling will be discussed in greater detail below. Since RRC signaling is well known, a detailed discussion will not be provided. Moreover, although example embodiments are discussed herein with respect to RRC signaling, example embodiments should not be limited to this example. Rather, other signaling mechanisms can be used.

[0068] Figure 2 is a signal flow diagram illustrating a method according to an example embodiment.

[0069] Reference Figure 2 At S202, the gNB 102 sends a UE capability enquiry (also 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 enquiry can include a request for the UE 106 to report a BCS “x” (also referred to as BCSx), etc. (e.g., sent to the gNB 102 via RRC signaling) by including a given bit (or set of bits) in a capability filter. The request can be, for example, capabilityRequestFilterCommon: IncludeBCS “x”. The BCS “x” or BCSx can be a fixed BCS number, such as x = 4, that is common to any band combination and can be used to inform the gNB 102 that the UE 106 supports one or more example embodiments described herein.

[0070] Assuming that the UE 106 supports the mechanisms discussed herein, at S204, the UE 106 synthesizes a capability container (ue-CapabilityRAT-Container) based on the request to report the 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:

[0071] CBWperBandperSCS: supported CBW for each NR band as a single band operation (this parameter can be optional depending on whether there is any CBW that satisfies this condition);

[0072] supportedBandwidthDL: supported maximum CBW for each NR band within the band combination; and

[0073] supportedMinBandwidthDL: supported minimum CBW for each NR band within the band combination.

[0074] The above-mentioned parameters can be known (or alternatively, (pre)programmed) at the UE and / or based on the capabilities of the UE 106. Further, the BCS information BCS_Info can be formatted according to the ASN. 1 notation used in the RRC specification. Since such format is known, a detailed discussion is omitted.

[0075] Still referring to Figure 2 At S206, the UE 106 sends the BCS information BCS_Info to the gNB 102. In at least one example, the UE 106 sends 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.

[0076] At S208, the gNB 102 receives the BCS information BCS_Info (e.g., included in the UE capability information RRC message) from the UE 106 and records / stores the BCS information BCS_Info in a memory at the gNB 102.

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

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

[0079] Still referring to Figure 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. Since the RRC (re)configuration messages and their exchange between a gNB and a UE are well known, only a brief discussion is provided below.

[0080] In more detail, at S212, the gNB 102 sends the RRC (re)configuration message including the determined CA configuration to the UE 106.

[0081] In response to the RRC (re)configuration message, the UE 106 performs the CA configuration (not shown). Once completed, at S214, the UE 106 sends an RRC reconfiguration complete message to the gNB 102 to indicate that the reconfiguration is complete.

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

[0083] If a given NR band does not support any CBW, the UE 106 can explicitly report the supported CBWs at the UE 106. That is, for example, in the case where the UE 106 supports as single-band operation a subset of all the specified channel bandwidths for each subcarrier spacing for each band, the UE 106 can provide as an explicit indication of single-band operation the channel bandwidths in the subset of all the specified channel bandwidths for each subcarrier spacing for each band.

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

[0085] Although the discussion is made with respect to downlink communications, the example embodiments should not be limited to this example. Rather, the example embodiments can also apply to uplink communications.

[0086] One 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 the example embodiments should not be limited to this example. This example will be discussed with reference to the signal flow diagrams in Figure 2 and the gNB 102 and UE 106 shown in Figure 1 .

[0087] In this example, the UE 106 can explicitly report the supported CBWs (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, the support of these CBWs is mandatory such that the UE 106 does not need to explicitly report these CBWs to the gNB 102.

[0088] In response to the UE capability enquiry (S202), at S206, the UE 106 reports at least the supported maximum CBW for each NR band within the band combination via the supportedBandwidthDL parameter in single band entries and single component carrier (CC) entries, such that the supportedBandwidthDL parameter is 20 MHz for the NR band n28 and 40 MHz for the NR band n75. Also at S206, the UE 106 reports the supported minimum CBW for each NR band within the band combination via the supportedMinBandwidthDL parameter in single band entries and single CC entries, such that the supportedMinBandwidthDL parameter is 10 MHz for the NR band n28 and 20 MHz for the NR band n75. The UE 106 can also include (i) an indication of a first supported channel bandwidth for each subcarrier spacing as a single band operation for the NR band n28 (first new radio band), and (ii) an indication of a second supported channel bandwidth for each subcarrier spacing as a single band operation for the NR band n75 (second new radio band).

[0089] After storing the reported capability information from the UE 106 (S208), at S210, the gNB 102 determines that for the NR band n28, the supported CBW for the band combination is in the range 10 MHz < CBW < 20 MHz. Thus, in this example, the gNB 102 determines that the UE 106 supports 10, 15, and 20 MHz bands for the NR band n28. For the NR band n75, the gNB 102 determines that, given the reported information, the supported CBW for the band combination is in the range 20 MHz < CBW < 40 MHz. Thus, the gNB 102 determines that 20, 25, 30, and 40 MHz bands are supported for the NR band n75.

[0090] Thus, in this example, the gNB 102 determines the supported CBW combinations for the band combination to be the combination of each supported CBW of each 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). Thus, in this example, the unsupported CBW combinations (n28, n75) = (5, 5), (5, 10), (5, 15) can be omitted by relatively simple (simpler) signaling.

[0091] Figure 3 An example implementation of a UE 106 is shown. Figure 1 An example implementation of a UE 106 is shown.

[0092] 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 constitute a transceiver to receive / transmit data from / to the gNB 102 via one or more wireless beams, or from / to multiple TRPs 102A, 102B, 102C, etc. As will be appreciated, depending on the implementation of the UE 106, the UE 106 can include far more components than those shown. However, for disclosing the illustrative example implementations, it is not necessary to show all of these common, conventional components. Figure 3 An example implementation of a UE 106 is shown.

[0093] The memory 740 can be a computer readable storage medium that generally includes random access memory (RAM), read only memory (ROM) and / or another persistent, large capacity memory such as a disk drive, depending on the implementation. The memory 740 also stores an operating system and any other routines / modules / applications to provide the functionality of the UE 106 (e.g., the functionality of the UE, methods according to example implementations, etc.) to be performed by the processor 720. These software components can also be loaded from a separate computer readable storage medium into the memory 740 using a drive mechanism (not shown). Such a separate computer readable storage medium can include a disk, a tape, a DVD / CD-ROM drive, a memory card, or other similar computer readable storage medium (not shown). In some example implementations, the software components can be loaded into the memory 740 via one of the various interfaces 760, rather than via a computer readable storage medium.

[0094] Processor 720 can be configured to execute instructions of a computer program by performing arithmetic, logical, and input / output operations of the system. Instructions can be provided to processor 720 by memory 740.

[0095] Various interfaces 760 may include components that interface the processor 720 with the antenna 765, or other input / output components. As will be understood, the various interfaces 760 and the programs stored in the memory 740 to articulate the specific functions of the UE 106 will vary depending on the implementation of the UE 106.

[0096] Interface 760 may also include one or more user input devices (e.g., keyboard, keypad, mouse, etc.) and user output devices (e.g., display, speaker, etc.).

[0097] Although not specifically discussed in this article, Figure 3 The configuration shown is particularly suitable for implementing TRP 102A, 102B, 102C, gNB 102, other radio access and backhaul network elements and / or devices. In this regard, for example, memory 740 may store the operating system and any other routines / modules / applications to provide the functionality of the TRP, gNB, etc. (e.g., the functions of these elements, methods according to the example implementation, etc.) to be executed by processor 720.

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

[0099] When an element is referred to as “connected” or “linked” to another element, the element may be directly connected or linked to the other element, or there may be intermediate elements. In contrast, when an element is referred to as “directly connected” or “directly linked” to another element, there are no intermediate elements. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., “between” vs. “directly between”, “adjacent” vs. “directly adjacent”, etc.).

[0100] 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 include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0101] It should also be noted that in some alternative implementations, the functions / acts described can occur out of the order noted in the figures. For example, two figures shown in succession can in fact be executed substantially concurrently or the figures can sometimes be executed in the reverse order, depending upon the functionality / acts involved.

[0102] In the following description, specific details are set forth to provide a thorough understanding of example implementations. However, persons having ordinary skill in the art will understand that the example implementations can be practiced without these specific details. For example, systems can be shown in block diagrams in order not to obscure the example implementations in unnecessary detail. In other instances, well-known processes, structures and techniques have not been shown in detail in order not to obscure the example implementations.

[0103] As discussed herein, illustrative embodiments will be described with reference to symbolic representations of operations (e.g., in the form of flowcharts illustrations, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.) that can be implemented with program modules or functional processes including routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types and can be implemented using existing hardware at existing user devices, base stations, eNBs, RRHs, gNBs, femto base stations, network controllers, computers, etc. Such existing hardware can 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 a chip (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), or any one or more other devices capable of responding to and executing instructions in a defined manner.

[0104] Although flow diagrams can describe operations as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations can be re-arranged. A process can be terminated when its operations are completed, but can also terminate unexpectedly due to system or other failures. Processes might correspond to methods, functions, application programs, routines, subroutines, etc. When a process corresponds to a function, its termination might correspond to a return of the function to the calling function or the main function.

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

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

[0107] A code segment, by way of example, can represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures or program statements. A code segment can 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. can be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0108] The terms "comprise" and / or "comprising," as used herein, are defined as open-ended (i.e., meaning "including, but not limited to") The term "coupled," as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. Terms derived from the word "indicating" (e.g., "indicates" and "indication") are intended to encompass all of the different techniques that can be used to convey or reference the object / information being indicated. Some, but not all, examples of techniques that can be used to convey or reference the object / information being indicated include an expression of the object / information being indicated, an expression of an identifier of the object / information being indicated, an expression of information used to produce the object / information being indicated, an expression of some portion or part of the object / information being indicated, an expression of some derivative form of the object / information being indicated, and an expression of some symbol representative of the object / information being indicated.

[0109] According to example embodiments, a user equipment, a base station, an eNB, a RRH, a gNB, a femto base station, a network controller, a computer, etc. can be (or include) hardware, firmware, hardware executing software, or any combination thereof. Such hardware can 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 one or more other devices capable of responding to and executing instructions in a defined manner.

[0110] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems and any element(s) that causes or contributes to such benefits, advantages, or solutions, or causes or contributes to making one or more of the benefits, advantages, or solutions more pronounced, are not to be construed as a critical, required, or essential feature or element of any or all the claims.

Claims

1. A radio access network element comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause 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 at least a supported maximum channel bandwidth information and a supported minimum channel bandwidth information for each subcarrier spacing of at least one component carrier for each frequency band within a frequency band combination, the frequency band combination including a first new radio frequency band and a second new radio frequency band; and send the carrier aggregation configuration to the user equipment to configure the user equipment to communicate with the radio access network element based on the capability information.

2. The radio access network element of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the radio access network element to generate the carrier aggregation configuration without storing a definition of each set of bandwidth combinations supported by the user equipment.

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

4. The radio access network element of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the radio access network element to send a capability query requesting the capability information from the user equipment.

5. The radio access network element of claim 1, wherein the capability information includes an indication that the capability information includes information identifying supported channel bandwidths for each frequency band within the frequency band combination.

6. The radio access network element of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the radio access network element to send the carrier aggregation configuration to the user equipment as a radio resource control message.

7. The radio access network element of claim 1, wherein the supported maximum channel bandwidth information includes (i) a first supported maximum channel bandwidth for each subcarrier spacing of the first new radio frequency band, and (ii) a second supported maximum channel bandwidth for each subcarrier spacing of the second new radio frequency band, the supported minimum channel bandwidth information includes (i) a first supported minimum channel bandwidth for each subcarrier spacing of the first new radio frequency band, and (ii) a second supported minimum channel bandwidth for each subcarrier spacing of the second new radio frequency band, and the carrier aggregation configuration includes a first supported maximum channel bandwidth for each subcarrier spacing of the first new radio frequency band, a second supported maximum channel bandwidth for each subcarrier spacing of the second new radio frequency band, a first supported minimum channel bandwidth for each subcarrier spacing of the first new radio frequency band, and a second supported minimum channel bandwidth for each subcarrier spacing of the second new radio frequency band. The carrier aggregation configuration comprises a combination of a first supported channel bandwidth per subcarrier spacing for the first new radio frequency band and a second supported channel bandwidth per subcarrier spacing for the second new radio frequency band.

8. A method for communication, comprising: generating a carrier aggregation configuration for a user equipment based on capability information from the user equipment, the capability information comprising at least supported maximum channel bandwidth information and supported minimum channel bandwidth information per subcarrier spacing for at least one component carrier per frequency band within a frequency band combination, the frequency band combination comprising a first new radio frequency band and a second new radio frequency band; and transmitting the carrier aggregation configuration to the user equipment based on the capability information to configure the user equipment to communicate with a radio access network element.

9. A user equipment, comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the user equipment to generate capability information about the user equipment, the capability information comprising at least supported maximum channel bandwidth information and supported minimum channel bandwidth information per subcarrier spacing for at least one component carrier per frequency band within a frequency band combination, the frequency band combination comprising a first new radio frequency band and a second new radio frequency band, transmit the capability information to a radio access network element, and in response to the transmission, receive a carrier aggregation configuration based on the capability information, and the carrier aggregation configuration configures the user equipment to communicate with the radio access network element.

10. The user equipment of claim 9, wherein the user equipment supports a subset of all specified channel bandwidths per subcarrier spacing per frequency band as a single frequency band operation, and the capability information comprises an indication of a channel bandwidth in the subset of all specified channel bandwidths per subcarrier spacing per frequency band as the single frequency band operation.

11. The user equipment of claim 9, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the user equipment to generate the capability information in response to a capability query from the radio access network element.

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

13. The user equipment of claim 9, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the user equipment to transmit the capability information to the radio access network element via radio resource control signaling.

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

15. A method for communication, comprising: generating capability information regarding a user equipment, the capability information including at least supported maximum channel bandwidth information and supported minimum channel bandwidth information per subcarrier spacing for each component carrier of each frequency band within a frequency band combination, the frequency band combination including a first new radio frequency band and a second new radio frequency band; transmitting the capability information to a radio access network element; and in response to the transmitting, receiving a carrier aggregation configuration based on the capability information, and the carrier aggregation configuration configuring the user equipment to communicate with the radio access network element.

Images