User device capability information for carrier grouping in dual connectivity

Abstract

To provide an apparatus, a device including a system and a method, and a component for configuring user equipment (UE) for dual connectivity.SOLUTION: In a dual connectivity environment 200, a network node requests UE to indicate its supporting capabilities for dual connectivity. This request can implicitly or explicitly indicate that the UE is to report carrier grouping information. In response, this information is transmitted by the UE, and the network node configures carriers for the UE into a master cell group (MCG) and a secondary cell group (SCG) on the basis of the reported carrier grouping information.SELECTED DRAWING: Figure 2

Description

Background Art

[0001] The fifth generation mobile network (5G) is a wireless standard aimed at improving data transmission rate, reliability, availability and the like. This standard is still under development, and includes many details related to cell reselection. For example, a User Equipment (UE) may communicate with a network using carriers in different frequency bands, and these frequency bands may belong to different frequency ranges.

Brief Description of the Drawings

[0002] [Figure 1] An example of a network environment according to some embodiments is shown.

[0003] [Figure 2] An example of a dual connectivity environment according to some embodiments is shown.

[0004] [Figure 3] An example of a sequence diagram illustrating signaling related to band combinations between a User Equipment (UE) and a network node according to some embodiments is shown.

[0005] [Figure 4] An example of a sequence diagram illustrating signaling between a UE and a network node for inquiring about UE capabilities related to carrier grouping according to some embodiments is shown.

[0006] [Figure 5] Another example of a sequence diagram illustrating signaling between a UE and a network node for inquiring about UE capabilities related to carrier grouping according to some embodiments is shown.

[0007] [Figure 6]Here is yet another example of a sequence diagram showing signaling between a UE and network nodes for querying UE capabilities with respect to carrier grouping, according to several embodiments.

[0008] [Figure 7] Further examples of sequence diagrams showing signaling between a UE and network nodes for querying UE capabilities with respect to carrier grouping, according to several embodiments, are provided.

[0009] [Figure 8] An example of a sequence diagram showing signaling between a UE and network nodes for reporting UE capabilities related to carrier grouping, according to several embodiments, is shown.

[0010] [Figure 9] Another example of a sequence diagram showing signaling between a UE and network nodes for reporting UE capabilities with respect to carrier grouping, according to several embodiments, is shown.

[0011] [Figure 10] Here is yet another example of a sequence diagram showing signaling between a UE and network nodes for reporting UE capabilities with respect to carrier grouping, according to some embodiments.

[0012] [Figure 11] The following are examples of the operational flow / algorithm structure of network nodes constituting carrier grouping according to several embodiments.

[0013] [Figure 12] This shows an example of a UE operation flow / algorithm structure that reports UE capabilities related to carrier grouping, according to several embodiments.

[0014] [Figure 13] An example of a receiving component according to several embodiments is shown.

[0015] [Figure 14] 1 shows an example of a UE according to some embodiments.

[0016] [Figure 15] 2 shows an example of a base station according to some embodiments. [Mode for Carrying Out the Invention]

[0017] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details such as particular structures, architectures, interfaces, and techniques are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present disclosure, "A or B" means (A), (B), or (A and B).

[0018] Typically, user equipment (UE) can communicate with one or more base stations or other network nodes, such as a network, using carriers (also called component carriers - CC) within different bands (also called frequency bands). These different bands can belong to different frequency ranges (FR), including, for example, Frequency Range 1 (FR1) from 450 MHz to 6000 MHz, Frequency Range 2 (FR2) from 24.25 GHz to 52.6 GHz, and / or another frequency range starting from 52.6 GHz. A UE can support specific band combinations of these bands. A UE can also support dual connectivity, allowing it to communicate simultaneously with multiple network nodes by using bands from a band combination, one of which may be a master node (also called a primary node) and another a secondary node. A Master Cell Group (MCG) (also called a Primary Cell Group) can be configured for the UE, provided by the master node, each containing multiple carriers corresponding to the serving cells of the MCG. Similarly, a Secondary Cell Group (SCG) can be configured for the UE, provided by the secondary node, each containing multiple other carriers corresponding to the serving cells of the SCG.

[0019] Information is exchanged between a UE and a network (e.g., a master node) to configure an MCG and an SCG for the UE. This information may indicate whether the UE supports dual connectivity for each band combination. For a band combination supported by the UE for dual connectivity, the information may further indicate whether the UE can support specifically grouping the carrier(s) from the bands of the band combination within (e.g., the MCG, the SCG, or both the MCG and the SCG).

[0020] In certain situations, the number of band combinations supported by the UE for dual connectivity may be large. Furthermore, the number of carriers that can be grouped within a cell group for each supported band combination may be large. Thus, the amount of information exchanged between the UE and the network also becomes large, which may increase signaling overhead. To improve signaling overhead (e.g., reduce the amount of information), the network (e.g., a master node) may be configured to indicate to the UE a request regarding the UE's carrier grouping capability related to dual connectivity. Upon receiving such a request, the UE may transmit its carrier grouping information.

[0021] Different variations of this approach may be implemented individually or jointly. In an example, the request may simply indicate that the network node does not support default carrier grouping (e.g., carriers in FR1 bands are grouped in the MCG, and carriers in FR2 bands are grouped in the SCG). In another example, the request may indicate specific bands that the network deploys for dual connectivity. In yet another example, the request may further indicate whether each such specific band is associated with a synchronous dual connectivity deployment or an asynchronous dual connectivity deployment.

[0022] Similarly, UEs can report capability information at different levels of granularity. In one example, a UE reports its full set of carrier grouping information (for example, only in response to one of the network node requests mentioned above). In another example, a UE includes only information about the carrier groups the network can form. In yet another example, a UE may indicate negative capabilities, such as carrier groups it does not support, or carrier groups the network can otherwise form. In yet another example, a UE may indicate UE requirements and / or constraints, such as grouping or not grouping carriers from a particular band together in the same cell group. These and other variations are further described below in this specification.

[0023] The following is a glossary of terms that may be used in this disclosure.

[0024] As used herein, the term “circuit configuration” refers to, part of, or includes hardware components such as electronic circuits, logic circuits, (shared, dedicated, or group) processors or (shared, dedicated, or group) memories, application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs) configured to provide the described functionality. In some embodiments, the circuit configuration may run one or more software or firmware programs to provide at least some of the described functionality. The term “circuit configuration” may also refer to a combination of program code and one or more hardware elements (or a combination of circuits used in an electrical or electronic system) for executing the functionality of the program code. In these embodiments, the combination of hardware elements and program code may be called a particular type of circuit configuration.

[0025] As used herein, the term "processor circuit configuration" refers to, a part of, or includes a circuit configuration capable of sequentially and automatically performing a series of arithmetic or logical operations or the recording, storage, or transfer of digital data. The term "processor circuit configuration" may also refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or operating computer executable instructions such as program code, software modules, or functional processes.

[0026] As used herein, the term “interface circuit configuration” refers to, is part of, or includes a circuit configuration that enables the exchange of information between two or more components or devices. The term “interface circuit configuration” may refer to one or more hardware interfaces, such as a bus, I / O interface, peripheral component interface, or network interface card.

[0027] As used herein, the terms “User Equipment” or “UE” refer to a device having wireless communication capabilities and may represent a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, or refer to, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless equipment, reconfigurable wireless equipment, reconfigurable mobile device, etc. Furthermore, the terms “User Equipment” or “UE” may include any computing device including any type of wireless / wired device or wireless communication interface.

[0028] As used herein, the term “base station” refers to a network node (or, more simply, a network) of a communication network, a device with wireless communication capabilities that can be configured as an access node in the communication network. Access of a UE to the communication network may be managed at least partially by a base station, thereby enabling the UE to connect to the base station for access to the communication network. Depending on the Radio Access Technology (RAT), a base station may be called a gNodeB (gNB), eNodeB (eNB), access point, etc.

[0029] As used herein, the term “computer system” refers to any kind of interconnected electronic devices, computer devices, or components thereof. In addition, the term “computer system” or “system” may refer to various components of a computer that are connected to one another in a communicative manner. Furthermore, the term “computer system” or “system” may refer to a group of computer devices or a group of computing systems that are connected to one another in a communicative manner and configured to share computing resources or networking resources.

[0030] As used herein, the term “resource” means a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, I / O operation, port or network socket, channel / link allocation, throughput, memory usage, storage, network, database and application, workload unit, etc. “Hardware resource” may mean a computing resource, storage resource, or network resource provided by one or more physical hardware elements. “Virtualization resource” may mean a computing resource, storage resource, or network resource provided to an application, device, system, etc., by a virtualization infrastructure. The term “network resource” or “communication resource” may mean a resource accessible by a computer device / system via a communication network. The term “system resource” may mean any kind of shared entity providing a service, and may include computing resources or network resources. System resources may be thought of as a set of coherent functions, network data objects, or services that reside on a single host or multiple hosts and are accessible through a clearly identifiable server.

[0031] As used herein, the term “channel” refers to a tangible or intangible transmission medium used to communicate data or a data stream. The term “channel” may be synonymous or equivalent to any other similar term indicating a path or medium through which data is communicated, such as “communication channel,” “data communication channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” or any other similar term. In addition, as used herein, the term “link” refers to a connection between two devices for the purpose of sending and receiving information.

[0032] As used herein, terms such as "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the specific occurrence of an object that may occur, for example, during the execution of program code.

[0033] The term "connected" can mean that two or more elements in a common communication protocol layer have a signaling relationship established with each other via a communication channel, link, interface, or reference point.

[0034] As used herein, the term “Network Element” refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “Network Element” may be considered synonymous with, or referred to as, networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0035] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or data element that contains content. An information element may contain one or more further information elements.

[0036] Figure 1 shows a network environment 100 according to several embodiments. The network environment 100 may include a UE 104 and a gNB 108. The gNB 108 may be a base station that provides a wireless access cell through which the UE 104 communicates with the gNB 108, such as a Third Generation Partnership Project (3GPP®) New Radio (NR) cell. The UE 104 and gNB 108 may communicate via an air interface compliant with 3GPP technical specifications, such as those defining the fifth-generation (5G) NR system standard.

[0037] The gNB108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and transport channels onto physical channels. Logical channels can transfer data between the Radio Link Control (RLC) layer and the MAC layer, transport channels can transfer data between the MAC layer and the PHY layer, and physical channels can transfer information via the air interface. Physical channels may include Physical Broadcast Channels (PBCH), Physical Downlink Control Channels (PDCCH), and Physical Downlink Shared Channels (PDSCH).

[0038] The PBCH may be used to broadcast system information that UE104 can use for initial access to the serving cell. The PBCH may be transmitted within a Synchronization Signal (SS) / PBCH block along with a Physical Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The SS / PBCH Block (SSB) may be used by UE104 during cell search procedures (including cell selection and re-search) and for beam selection.

[0039] PDSCH can be used to transfer end-user application data, signaling radio bearer (SRB) messages, system information messages (e.g., non-MIB messages), and paging messages.

[0040] The PDCCH can forward DCIs used by the gNB108's scheduler to allocate both uplink and downlink resources. DCIs can also be used to provide uplink power control commands, configure slot formats, or indicate when preemption occurs.

[0041] The gNB108 can also transmit various reference signals to the UE104. These reference signals may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. The UE104 may compare the received version of the DMRS to a transmitted known DMRS sequence in order to estimate the influence of the propagation channel. The UE104 may then apply the inverse of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0042] The reference signal may also include a Channel Status Information Reference Signal (CSI-RS). The CSI-RS may be a multi-purpose downlink transmitter that can be used for CSI reporting, beam management, connection mode mobility, radio link fault detection, beam fault detection and recovery, and fine-tuning of time and frequency synchronization.

[0043] Reference signals and information from a physical channel can be mapped to resources in a resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), one resource grid exists. The basic unit of an NR downlink resource grid may be a resource element, defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain may constitute a physical resource block (PRB). A resource element group (REG) may include one PRB in the frequency domain, one OFDM symbol in the time domain, and, for example, twelve resource elements. A control channel element (CCE) may represent a group of resources used to transmit a PDCCH. One CCE may be mapped to several REGs, for example, six REGs.

[0044] UE104 can transmit data and control information to gNB108 using a physical uplink channel. Different types of physical uplink channels are available, including, for example, a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH). PUCCH carries control information such as Uplink Control Information (UCI) from UE104 to gNB108, while PUSCH can carry data traffic (e.g., end-user application data) and UCI.

[0045] UE104 and gNB108 can perform beam management operations to identify and maintain the desired beam for transmission in the uplink and downlink directions. Beam management can be applied to both PDSCH and PDCCH in the downlink direction, as well as PUSCH and PUCCH in the uplink direction.

[0046] For example, communication with the gNB108 and / or base station may use channels within frequency range 1 (FR1), frequency range 2 (FR2), and / or a higher frequency range (FRH). The FR1 band includes licensed and unlicensed bands. The NR Unlicensed band (NR-U) includes frequency spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). To avoid or minimize collisions between different RATs in the NR-U, a listen-before-talk (LBT) procedure may be used, which requires the device to apply a Clear Channel Assessment (CCA) check before using the channel.

[0047] As further shown in Figure 1, the network environment 100 may further include a base station 112 to which the UE 104 can also connect. The base station 112 supports the same RAT as the gNB 108 (for example, base station 112 is also a gNB). In addition or instead, base station 112 supports a different RAT (for example, Long-Term Evolution (LTE) eNB).

[0048] For example, UE104 supports Carrier Aggregation (CA), which allows UE104 to simultaneously connect with gNB108 or base station 112 via multiple component carriers (CCs) and exchange data. CCs can belong to the same frequency band, in which case they are called in-band CCs. In-band CCs can be continuous or discontinuous. CCs can also belong to different frequency bands, in which case they are called inter-band CCs. A serving cell can be configured for UE104 to use CCs. A serving cell may be a primary cell (PCell) or a secondary cell (SCell). Multiple SCells can be activated via an SCell activation procedure, and the component carriers of these serving cells can be continuous within the band, discontinuous within the band, or inter-band. Serving cells can be collocated or non-collocated.

[0049] The UE104 can also support Dual Connectivity (DC), which allows simultaneous transmission and reception of data on multiple CCs from two serving nodes or cell groups (Master Node (MN) and Secondary Node (SN)). DC capability can be used with two serving nodes operating in the same or different RATs (e.g., MN operating in NR, SN operating in LTE). These different DC modes include, for example, Evolved-universal terrestrial radio access-New radio (EN)-DC, NR-DC, and NE-DC (where MN is an NR gNB and SN is an LTE eNB).

[0050] Figure 2 shows an example of a dual connectivity environment 200 according to several embodiments. Typically, dual connectivity (also called DC) is an operating mode in which the UE 210 is configured to use the radio resources of two network nodes connected via backhaul, called a master node (MN) and a secondary node (SN). Dual connectivity allows the UE 210 to simultaneously transmit and receive data on multiple carriers from two cell groups via the MN and SN. In one example, each of the MN and SN can be a gNB or an eNB. The cell groups can be a master cell group (MCG) provided by the MN and a secondary cell group (SCG) provided by the SN.

[0051] In the example in Figure 2, UE210, similar to UE104 in Figure 1, maintains two connections: one to MCG220 and one to SCG230. MCG220 contains multiple carriers, each corresponding to a serving cell for UE210. While the PCell is activated, the remaining serving cells in MCG220 may or may not be activated. Similarly, SCG230 contains multiple carriers, each corresponding to a serving cell for UE210. While the primary cell within SCG230 (also called the primary secondary cell (PSCell)) is activated, the remaining serving cells in SCG230 may or may not be activated. UE210 supports simultaneous reception and transmission through its two connections to MCG220 and SCG230 (also called the primary leg and secondary leg). Split-bearer scenarios can also be supported, allowing transmission via the primary leg alone to suffice for small data volumes, while transmission via both legs is possible for larger data volumes.

[0052] As described above, each of the MN and SN can be either a gNB or an eNB. This can result in different deployment configurations for the MCG220 and SCG230. These configurations include LTE-LTE DC, LTE-NR DC, NR-LTE DC, and NR-NR DC. Furthermore, they can provide synchronous and asynchronous communication in dual connectivity. In synchronous NR-DC, the MCG220 and SCG230 have aligned frames and slots (for example, the serving cells within these two cell groups are synchronized). Conversely, in asynchronous NR-DC, the MCG220 and SCG230 do not need to have aligned frames and slots (for example, the serving cells within these two cell groups do not necessarily need to be synchronized).

[0053] In one example, MCG220 and SCG230 each contain different sets of carriers from the same or different sets of bands. This can result in intraband DC, interband DC, and interband DC with an intraband component. In an intraband DC, carriers from the same band are present in MCG220 and SCG230. In contrast, in an interband DC, carriers from different bands are present in MCG220 and SCG230. An interband DC with an intraband component can be a hybrid of intraband DC and interband DC, where carriers from different bands are present in MCG220 and SCG230, while the cell group (e.g., MCG220, SCG230, or both) contains carriers from the same band.

[0054] For illustrative purposes, consider the following example. Typically, LTE bands are numbered by band number (for example, LTE-1_2 indicates carrier aggregation using "LTE Band 1" and "LTE Band 2"). NR bands are numbered similarly, but with "n" added as a prefix to the band number (for example, DC-n1_n2 indicates dual connectivity using "NR Band n1" and "NR Band n2"). In this example, MN is eNB and SN is gNB, corresponding to an EN-DC deployment (E-UTRA-NR dual connectivity). DC-1_4_n1_n260 indicates that the EN-DC uses two LTE bands: "LTE Band 1" and "LTE Band 2," and two NR bands: "NR Band n1" and "NR Band n260"). This example corresponds to an inter-band EN-NR DC deployment. In another example, the deployment uses DC(n)1_n256 and corresponds to an inter-band EN-NR DC with an in-band component. Here, "LTE Band 1" and "NR Band n1" are within the same band, while "NR Band n1" and "NR Band 256" are between bands.

[0055] In supporting dual connectivity, the UE210 reports its ability to support band combinations. A band combination corresponds to a set of two or more bands from the same or different frequency ranges (e.g., LTE and / or NR bands from FR1 and / or FR2, where applicable). For example, a band combination might be denoted as "n1,n2,n3" and correspond to a combination of three NR bands from FR1, namely "NR band nb1", "NR band n2", and "NR band n3".

[0056] For each band combination, the UE210 reports whether it supports the band combination for dual connectivity. In other words, the UE210 can indicate whether the carriers within the bands of the band combination are supported by the UE210 for dual connectivity. For example, the UE210 reports UE capability information to the network (e.g., MN) indicating that it supports the band combination "n1,n2,n3" for dual connectivity. In this case, the network can configure carriers (e.g., serving cells) from the corresponding NR bands (e.g., "NR band n1", "NR band n2", and "NR band n3") for the UE210's dual connectivity.

[0057] For example, in addition to, or instead of, demonstrating support for band combinations for dual connectivity, the UE210 may demonstrate its support for carrier grouping between the MCG220 and SCG230 by sending carrier grouping information. Carriers from carrier grouping (also called carrier grouping) are from bands that the UE210 supports for band combinations in dual connectivity. The UE210 indicates how these carriers can be grouped with the MCG220 and SCG230. The carrier grouping information does not need to identify the carriers. Instead, the carrier grouping information can indicate the bands of the band combination and how a first subset of these bands can be associated with the MCG220, and how a second subset of these bands can be associated with the SCG230. The network can then be configured to assign carriers in the bands from the first subset (e.g., serving cells) to the MCG220 and carriers in the bands from the second subset (e.g., serving cells) to the SCG230. Continuing with the example of the band combination "n1, n2, n3", the carrier grouping information can indicate that the UE supports the grouping of one or more carriers in "NR band n1" and "NR band n2" within the MCG220, and one or more carriers in "NR band n3" within the SCG230. Therefore, the network can configure the MCG220 to include one or more carriers in "NR band n1" and / or "NR band n2", and the SCG230 to include one or more carriers in "NR band n3".

[0058] If such carrier grouping information is not reported, the network may assume a default carrier grouping. For example, the default may be that for a supported band combination, carriers from the FR1 band can be grouped to MCG220, while carriers from the FR2 band can be grouped to SCG230. This type of reporting and / or default assumption can be used for each band combination supported by the UE for dual connectivity.

[0059] Figure 3 shows an example of a sequence diagram 300 illustrating signaling for band combinations between the UE310 and the network node 320 according to several embodiments. Typically, the sequence diagram 300 can be used to configure the UE310 for dual connectivity, where applicable, based on the UE310's ability to be associated with dual connectivity.

[0060] As shown in the figure, sequence diagram 300 includes initiating a capability transfer procedure during the registration of UE310 to the network via network node 320 of the network. This procedure can be initiated for UE310 if it is determined that one or more access criteria are met. These criteria may relate to cell measurement, handover procedures, cell reselection, network roaming, and / or other procedures for registering UE310 to the network. The capability transfer procedure includes a Random Access (RACH) procedure for UE310 to establish an initial connection with the network. For example, a System Information Block (SIB) is sent from network node 320. In response, UE310 initiates a new session with a randomly selected preamble. Network node 320 responds with a Random Access Response message. Next, UE310 sends an RRC Connection Request message, and network node 320 responds with an RRC Connection Setup message. Then, UE310 sends an RRC Connection Setup message which may indicate that UE310 supports dual connectivity.

[0061] Since dual connectivity is supported, network node 320 checks the network, for example by querying the network's core network 330, whether UE capability information for UE 310 regarding dual connectivity is available (e.g., previously stored by the core network 330). This capability check is shown as a capability lookup in Figure 3. If it is not available, RRC signaling is exchanged between network 320 and UE 310 to determine UE capability information, including UE support for the band combination for dual connectivity. The RRC signaling of network node 320 may have multiple Information Elements (IEs) and may include a UE capability query that can be sent to UE 310 in the RRC request message. In response, UE 310 sends its UE capability information, which may also have multiple IEs, that can be sent in the RRC response message. Network node 320 passes this information to the core network 330 for storage. Otherwise, network node 320 does not need to receive UE capability information 310 from UE 310, and can instead use information retrieved from core network 330.

[0062] Once UE capability information is determined (e.g., from UE310 or core network330), network node 320 can configure various resources for UE310 based on the UE capability information. This may include activating a default radio bearer, configuring measurement objects, transmitting reference signals, etc. In addition, in the case of dual connectivity, this may also include configuring MCG and SCG for the UE. This configuration may rely on RRC signaling, for example, one or more RRC connectivity reconfiguration messages. For example, network node 320 may allocate a carrier (e.g., a serving cell) for the MCG and send a node add request to a second node in the network to add the second node as an SN (in this case, network node 320 is the MN). This SN may allocate a carrier (e.g., a serving cell) for the SCG and respond to network node 320 with a node add request acknowledgment indicating the serving cells (e.g., various resources) for the SCG. Next, the network node 320 can send one or more RRC connection reconfiguration messages to the UE310 indicating the MCG and SCG resources.

[0063] As described herein, the UE310 can support one or more band combinations for dual connectivity. Furthermore, the UE310 can be pre-configured to support specific carrier groupings for each band combination. This may depend, for example, on the UE310's radio frequency (RF) hardware. In addition, the UE310 can receive over-the-air (OTA) updates from service providers (e.g., mobile network operators) to disable certain bands. Thus, the UE310 may maintain an internal data structure (e.g., a table) showing different variants for each band combination. Each variant indicates how the carriers in the bands of the band combination can be grouped within the MCG and SCG configured by the network node 320 for the UE310 when they are allocated by the network node 320.

[0064] To illustrate this data structure, consider the example band combination n2A_n5A_n256A_n260_n260. This band combination is an NR band combination of four NR bands, one of which is repeated twice to show that continuous and discontinuous carriers can be allocated from such NR bands. Specifically, the NR bands are "NR band n2A", "NR band n5A", "NR band n256", and the repeated "NR band n260". The UE310 can maintain the following data structure (shown as a table, but other types of data structures such as strings and arrays are also possible). [Table 1]

[0065] In the table above, "Variant 1" indicates that the UE310 supports one or more carriers from "NR Band 2A" assigned to the MCG, and one or more carriers from each of "NR Band 5A", "NR Band 256A", and "NR Band 260A" assigned to the SCG. Each of the remaining variants indicates that the UE310 supports assigning different sets to the MCG and SCG (for example, each set representing a carrier grouping). If the default MCG-SCG allocation is such that carriers from the FR1 band are grouped within the MCG and carriers from the FR2 band are grouped within the SCG (for example, the configuration used by network node 320 when UE310 does not provide that carrier grouping information), then "Variant 5" indicates that UE310 supports this default (because "NR Band 2A" and "NR Band 5A" are in the FR1 band and should be carrier-grouped within the MCG, and "NR Band 256A" and "NR Band 260A" are in the FR2 band and should be carrier-grouped within the SCG).

[0066] The carrier grouping information described above can be maintained within the data structure for each band combination supported by the UE310 for dual connectivity. The size of the data structure (e.g., the amount of carrier grouping information) can be large because the number of permutations in which different carriers can be grouped (e.g., the number of possible variants) can be large. Roughly speaking, for a band combination of "n" different carriers (where each carrier is from a different band), the number of ways in which carriers can be grouped within the MCG and SCG is approximately n! ((1! × 2!)). In the above example of a band combination consisting of five bands, this number corresponds to 60 possible carrier groupings (e.g., 60 variants) in the MCG and SCG. This number can increase if continuous and discontinuous variants are considered.

[0067] If the UE310 reports carrier grouping information (e.g., information about variants) for each of the band combinations it supports for dual connectivity, the amount of information reported can be substantial. In other words, overhead signaling can be significant.

[0068] Various techniques can be used to reduce this overhead, which will be further explained in relation to the following diagram. At the lowest level of granularity, UE310 can report the full set of carrier grouping information only when requested by network node 310. At the highest level of granularity, UE310 can report a subset of carrier grouping information, which is specific to the deployment(s) of band combinations for dual connectivity by the network. The level of granularity at which carrier grouping information is reported by UE310 can depend on the request of network node 320. The more parameters this request has, the higher the level of granularity. In particular, UE310 can use the(s) parameters from the request as filters to search the data structure, determine matches, and report the matched information to network node 320. For example, UE310 can store the logic of a query engine that uses the parameters in the query.The parameters are: whether network node 320 (or more generally the network) supports only the default MCG-SCG assignment; whether network node 320 (or more generally the network) supports non-default MCG-SCG assignments; the bands that network node 320 (or more generally the network) supports for dual connectivity band combinations; the bands that network node 320 (or more generally the network) does not support for dual connectivity band combinations; the band combinations that network node 320 (or more generally the network) supports for dual connectivity; and in dual connectivity... This may include any or all of the following: band combinations not supported by network node 320 (or more generally, the network); the set of bands supported by network node 320 (or more generally, the network) for synchronous deployment of dual connectivity; the set of bands supported by network node 320 (or more generally, the network) for asynchronous deployment of dual connectivity; and / or other parameters relating to how network node 320 (or more generally, the network) can deploy dual connectivity, band combinations in dual connectivity; bands in band combinations; and / or carriers in bands.

[0069] Figure 4 shows an example of sequence diagram 400 illustrating signaling between UE410 and network node 420 for querying UE capability regarding carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE410 and network node 420 are examples of UE310 and network node 320 in Figure 3, respectively. In this sequence diagram 400, network node 420 may simply indicate that it supports non-default MCG-SCG assignment. Only in response to this instruction does UE410 transmit its carrier grouping information. In other words, if network node 420 does not provide any additional information beyond its support for non-default MCG-SCG assignment, UE410 presents network node 420 with the full set of its variants.

[0070] Therefore, sequence diagram 400 is an example of a technique to ensure that the UE410 does not need to report carrier grouping for each band combination if the network is not intended to configure dual connectivity to the UE410. It is also possible that the network does not actually support dual connectivity configurations, in which case it would be useless for the UE to report all of its carrier grouping information. In this case, the UE410 will only report carrier grouping information if the network explicitly requests it to do so (assuming that the network actually supports different carrier groupings other than the default MCG-SCG assignment, which does not require the UE to signal carrier grouping information).

[0071] In one example, sequence diagram 400 includes network node 420 sending a UE capability query to UE 410, and UE 410 responding with UE capability information. The UE capability query is associated with UE 410's support for carrier grouping for dual connectivity. In one example, the UE capability query indicates that network node 420 supports grouping multiple carriers from different frequency ranges within the same cell group. For example, the query simply indicates that network node 420 supports non-default MCG-SCG assignments (or, conversely, does not support default MCG-SCG assignments). In another example, the UE capability query may include a request indicating that UE 410 should report its full set of carrier grouping information. Thus, in the UE capability information, the UE can indicate its supported band combinations (for example, for CA). For each supported band combination, the UE capability information can also indicate whether UE 410 supports using this band combination for dual connectivity. If available, UE capability information may indicate the corresponding portion of carrier grouping information (e.g., the full set of variants of band combinations supported by UE410 for dual connectivity). For example, UE capability information may indicate that UE410 supports grouping bands that form supported band combinations and are in different frequency ranges, and carriers from different frequency ranges, into the same cell group. Additional granularity may be provided, so that carrier grouping information indicates that UE supports grouping a first carrier in a first band of the bands into an MCG, and a second carrier in a second band of the bands into an SCG.

[0072] For illustrative purposes, consider the following example. In response to a UE capability query, the UE410 reports that it supports the band combination "n5,n6" for CA (Carrier Aggregation) and the band combination "n1,n3,n4" for DC (and CA). Since the band combination "n5,n6" is not supported for DC, the UE410 does not report carrier grouping information for this band combination. In contrast, since the band combination "n1,n3,n4" is supported for DC, the UE410 reports its grouping information for this band combination. In this case, assume that the UE410 supports two variants. The first variant is "NR band n1" assigned to an MCG (e.g., one or more carriers from it constitute the corresponding serving cell(s) within the MCG), and "NR bands n3" and "NR bands n4" assigned to an SCG (e.g., one or more carriers from it constitute the corresponding serving cell(s) within the SCG). The second variant includes "NR band n1" and "NR band n4" assigned to the MCG, and "NR band 3" assigned to the SCG. In this diagram, UE410 reports the first and second variants to network node 420. Similar carrier configuration information for other band combinations supported by the UE for dual connectivity can be reported to network node 420.

[0073] In response, network node 420 can store UE capability information (including reported carrier aggregation information) in the network (e.g., in the core network). Network node 420 can also configure MCG and SCG for UE 410 based on the reported carrier aggregation information. For example, using the first variant, network node 420 may configure a set of carriers in "NR band n1" as a set of serving cells in the MCG, and a set of carriers in "NR band n3" and / or "NR band n4" as a set of serving cells in the SCG.

[0074] Figure 5 shows another example of sequence diagram 500 illustrating signaling between UE 510 and network node 520 for querying UE capability regarding carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE 510 and network node 520 are examples of UE 310 and network node 320 in Figure 3, respectively. Sequence diagram 500 is complementary to sequence diagram 400 (wherein network node 520 differs from network node 420 in Figure 4, each such node may belong to a different network). In particular, if network node 520 does not request UE 510 to transmit its carrier grouping information, UE 510 may demonstrate its support for dual connectivity band combinations without reporting its carrier grouping information.

[0075] Therefore, sequence diagram 500 is another example of a technique to ensure that UE410 does not need to report carrier grouping for each band combination if the network is not intended to configure dual connectivity to UE510. For example, if UE510 roams to a network that does not support dual connectivity or non-default MCG-SCG assignment (and thus network node 520 does not request carrier grouping information), UE510 reports only UE capability information without its carrier grouping information, and thus saves the size of UE capability by appropriately retaining information within UE capability IE(s) or more.

[0076] In one example, sequence diagram 500 includes network node 520 sending a UE capability query to UE 510, and UE 510 responding with UE capability information. The UE capability query is related to UE 510's support for dual connectivity, rather than carrier grouping for dual connectivity. In one example, the UE capability query indicates that network node 520 does not support non-default MCG-SCG assignments (or, conversely, only supports default MCG-SCG assignments). In another example, the UE capability query excludes all requests indicating that UE 510 should report its full set of carrier grouping information. Thus, in the UE capability information, the UE can indicate its supported band combinations (for example, for CA). For each supported band combination, the UE capability information can also indicate whether UE 510 supports using this band combination for dual connectivity. However, in the case of such band combinations, the UE does not include the corresponding portion of the carrier grouping information (for example, the full set of variants of band combinations supported by the UE510 for dual connectivity).

[0077] For illustrative purposes, consider the following example. In response to a UE capability inquiry, UE510 reports that it supports the band combination "n1,n2" for CA (carrier array) and the band combination "n1,n3,n4" for DC (and CA). Since the band combination "n1,n2" is not supported for DC, UE510 does not report carrier grouping information for this band combination. Furthermore, although the band combination "n1,n3,n4" is supported for DC, UE510 still does not report its grouping information for this band combination because the UE capability inquiry did not request this information.

[0078] In response, network node 520 can store UE capability information in the network (e.g., in the core network) (as carrier aggregation information was not reported). Network node 520 does not configure an MCG or SCG for UE 510.

[0079] Figure 6 shows yet another example of sequence diagram 600, illustrating signaling between UE610 and network node 620 for querying UE capability regarding carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE610 and network node 620 are examples of UE310 and network node 320 in Figure 3, respectively. Compared to sequence diagram 400, the information exchange here is of a finer granularity. In this sequence diagram 600, network node 620 may indicate the set of bands that network node 620 (or more generally the network) supports for dual connectivity. In response to this instruction, UE610 transmits its carrier grouping information, here, as with sequence diagram 400 in Figure 4, the carrier grouping information can be the full set of variants supported by UE610. Alternatively, the UE610 can use band indicators as filters in the lookup of its data structure to report only the portion of the configuration information corresponding to the indicated band.

[0080] Therefore, sequence diagram 600 is an example of a technique in which CA is possible in the network due to several factors (e.g., the presence of MCG and SCG and inter-node coordination), but only a few bands used within a cell group (e.g., SCG) are useful for the actual deployment of dual connectivity by the network. In contrast, more bands / carriers may be available for CA. In this case, the network provides the bands that the network intends to use for the dual connectivity configuration, and UE610 provides carrier groupings based on this information. UE610 can skip carrier grouping information that the network does not support or does not intend to use to configure dual connectivity in some bands.

[0081] In one example, sequence diagram 600 includes network node 620 sending a UE capability query to UE 610, and UE 610 responding with UE capability information. The UE capability query is associated with UE 610's support for carrier grouping for dual connectivity. In one example, the UE capability query indicates network node 620's support for a set of band combinations for dual connectivity. For example, this query can identify not only the bands the network supports for CA, but also a subset of these bands the network supports for DC. Thus, in the UE capability information, the UE can indicate the band combinations it supports (for example, for CA). From these CA-supported band combinations, UE 610 can determine a subset of band combinations that UE 610 supports for DC. UE 610 can then cross-check this subset with the set of band combinations indicated by network 620 as supported for dual connectivity. Specifically, for each band combination within a subset, UE610 determines the bands of the combination and whether those bands are supported by network node 620 (or more generally, the network) for dual connectivity. If so, the band combination belongs to the final set. Otherwise, the band combination is not included in the final set. For each band combination within the final set, UE capability information may indicate that UE610 supports using this band combination for dual connectivity. Furthermore, UE capability information may indicate the corresponding portion of carrier grouping information (e.g., the full set of variants for that band combination).

[0082] For illustrative purposes, consider the following example. In a UE capability query, network node 620 indicates that it supports bands "n1,n2,n3,n4,n5" (for CA use, for example) and band "n1,n3,n4" only for DC use. In response, UE610 reports that it supports band combination "n1,n2" for CA use but not for DC, and band combination "n1,n3,n4" for DC (and CA). Since band combination "n1,n2" is not supported for DC, UE610 does not report carrier grouping information for this band combination. In contrast, since band combination "n1,n3,n4" is supported for DC, UE610 reports its grouping information for this band combination. In this case, we assume that UE610 supports two variants. The first variant is "NR band n1" assigned to the MCG (for example, one or more carriers from there constitute the corresponding serving cell(s) within the MCG), and "NR bands n3" and "NR bands n4" assigned to the SCG (for example, one or more carriers from there constitute the corresponding serving cell(s) within the SCG). The second variant is "NR bands n1" and "NR bands n4" assigned to the MCG, and "NR band 3" assigned to the SCG. In this diagram, UE610 reports the first and second variants to network node 620. Similar carrier configuration information for other band combinations supported by the UE for dual connectivity can be reported to network node 620.

[0083] In response, network node 620 can store UE capability information (including reported carrier aggregation information) in the network (e.g., in the core network). Network node 620 can also configure MCG and SCG for UE 610 based on the reported carrier aggregation information. For example, using a second variant, network node 620 may configure a set of carriers in "NR band n1" and / or "NR band n4" as a set of serving cells in the MCG, and a set of carriers in "NR band n3" as a set of serving cells in the SCG.

[0084] Figure 7 shows a further example of a sequence diagram illustrating signaling between a UE and a network node for querying UE capabilities regarding carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE 710 and network node 720 are examples of UE 310 and network node 320 in Figure 3, respectively. Compared to sequence diagram 600, the information exchange here is of a finer granularity. In this sequence diagram 700, network node 720 may indicate a set of bands that network node 720 (or more generally the network) supports for synchronous dual connectivity and a set of bands that network node 720 (or more generally the network) supports for asynchronous dual connectivity. In response to this instruction, UE 710 transmits its carrier grouping information, here, as with sequence diagram 400 in Figure 4, the carrier grouping information can be the full set of variants supported by UE 710. Alternatively, the UE710 can use the band indicators for synchronous DC and asynchronous DC as filters in the lookup of its data structure to report only the portions of the configuration information corresponding to the bands indicated for synchronous DC and the portions of the configuration information corresponding to the bands indicated for asynchronous DC.

[0085] Therefore, sequence diagram 700 is an example of a technique in which a network deployment of different carriers cannot support both asynchronous and synchronous versions of cell groups if some carriers have (or do not have) timing linkage. For example, if a network uses "NR band n1", "NR band n2", and "NR band n3", and "NR band n1" and "NR band n3" are not synchronized in time, the network cannot configure a synchronous NR-DC using "NR band n1" and "NR band n3". In this sequence diagram 700, the network provides a set of bands that the network intends to use only for synchronous DC deployments and a set of bands that the network intends to use for synchronous DC deployments. In response, UE710 indicates its supported carrier groupings based on this information. UE710 can skip carrier groupings that the network does not support and / or does not intend to configure.

[0086] In one example, sequence diagram 700 includes network node 720 sending a UE capability query to UE 710, and UE 710 responding with UE capability information. The UE capability query is associated with UE 710's support for carrier grouping for dual connectivity. In one example, the UE capability query indicates that network node 720 supports a set of band combinations for a synchronous deployment of dual connectivity. In addition or alternatively, the UE capability query indicates that the network node supports a set of band combinations for asynchronous deployment of dual connectivity. For example, the query not only identifies the bands that the network supports for CA and a subset of these bands that the network supports for DC, but also indicates which particular bands from the subset are available to network node 620 (or more generally the network) for a synchronous DC, and which other particular bands from the subset are available to network node 620 (or more generally the network) for asynchronous DC. Thus, in the UE capability information, the UE can indicate the band combinations it supports (for example, for CA). From these CA-supported band combinations, the UE710 can determine a subset of band combinations that the UE710 supports for DC. The UE710 can then cross-check this subset against the set of band combinations indicated by network 720 as supported for synchronous dual connectivity and the set of band combinations indicated by network 720 as supported for asynchronous dual connectivity. In particular, for each band combination in the subset, the UE710 determines the bands of the band combination and whether those bands are supported by network node 720 (or more generally, the network) for synchronous dual connectivity or asynchronous dual connectivity. If supported for a synchronous DC deployment, the band combination belongs to the first final set associated with the synchronous DC deployment.If supported for asynchronous DC deployments, the band combination belongs to a second final set associated with the asynchronous DC deployment. Otherwise, the band combination is not included in the first or second final set. For each band combination in the first final set, the UE capability information may indicate that the UE710 supports using this band combination for synchronous dual connectivity. For each band combination in the second final set, the UE capability information may indicate that the UE710 supports using this band combination for asynchronous dual connectivity. Furthermore, the UE capability information may indicate the corresponding portion of the carrier grouping information (e.g., the full set of variants for each band combination in the first and second final sets).

[0087] To illustrate, consider the following example. In a UE capability query, network node 720 indicates that it supports bands "n1,n2,n3,n4,n5,n6,n7" (for CA use, for example), bands "n1,n2" and "n4,n7" only for synchronous DC deployments, and band "n3,n5" for asynchronous DC deployments. In response, UE710 reports that it supports band combination "n1,n2" for CA but not for DC, and band combinations "n4,n7" and "n3,n5" for DC (and CA). Since band combination "n1,n2" is not supported for DC, UE710 does not report carrier grouping information for this band combination. In contrast, since band combination "n4,n7" is supported for DC, UE710 reports its grouping information for this band combination. Similarly, since the band combination "n3,n5" is supported for DC, the UE710 reports its grouping information for this band combination.

[0088] In response, network node 720 can store UE capability information (including reported carrier aggregation information) in the network (e.g., in the core network). Network node 720 can also configure the MCG and SCG for UE 710 based on the reported carrier aggregation information. For example, network node 720 may determine the supported variants associated with the "n4,n7" band combination and configure a set of carriers from there within the MCG and SCG for synchronous dual connectivity.

[0089] Figure 8 shows an example of sequence diagram 800 illustrating signaling between UE810 and network node 820 for reporting UE capability with respect to carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE810 and network node 820 are examples of UE310 and network node 320 in Figure 3, respectively. Compared to sequence diagrams 400-700, the reported UE capability information indicates negative capability. This negative capability can be reported in addition to, or instead of, carrier configuration information (e.g., positive capability information) described in relation to sequence diagrams 400-700. Typically, negative capability information is a type of carrier grouping information. However, UE810 indicates what it cannot support, rather than what it can support. For example, the UE capability information indicates the bands of the band combinations that UE810 supports for dual connectivity. This UE capability carrier grouping information may include negative capability information indicating that the UE810 cannot support grouping the first carrier from the first subset of the band into a cell group (e.g., MCG or SCG). In certain situations, the data size required to report negative capability is smaller than the data size required to report positive capability (e.g., that the UE810 can support). Therefore, reporting negative capability can further reduce signaling overhead.

[0090] Therefore, sequence diagram 800 is an example of a technique in which the UE810 may not be able to support only a small number of carrier groupings for DC (for example, if it supports a large number of variants and / or a large number of band combinations). In such cases, it would be beneficial to inform the network of the carrier groupings that the UE810 does not support, allowing the network to assume that all other carrier groupings are supported. Thus, as part of the UE capability response, the UE810 includes a set of negative support capabilities regarding carrier groupings, such as a set of carrier groupings it does not support, while allowing the network to assume that the UE810 supports all other carrier groupings.

[0091] In one example, sequence diagram 800 includes network node 820 sending a UE capability query to UE810, and UE810 responding with UE capability information. The UE capability query is associated with UE810's support for carrier grouping for dual connectivity. This query may be similar to any of the UE capability queries described in relation to sequence diagrams 400-700. In the example of Figure 8, the UE capability query is similar to that in sequence diagram 700, where network node 810 explicitly indicates the bands for synchronous and asynchronous dual connectivity. From this query, UE820 can determine the band combinations that UE820 supports for CA, a subset of these band combinations that UE820 supports for DC, and, where applicable, a division of this subset between the band combinations that UE810 supports for synchronous DC and the band combinations that UE810 supports for asynchronous DC. UE820 can report this positive capability. In addition or alternatively, UE820 can determine negative capabilities. For example, a subset of band combinations supported by the UE820 for DCs is associated with the total number of synchronous-independent variants. Band combinations supported for synchronous DCs are associated with a first number of synchronous DC-supported variants. Similarly, band combinations supported for asynchronous DCs are associated with a first number of asynchronous DC-supported variants. Negative capabilities correspond to negative variants, which are the difference between synchronous-independent variants and the variants supported for synchronous and asynchronous DCs. In UE capability information, the UE820 can indicate these negative variants.

[0092] For illustrative purposes, consider the following example. In a UE capability query, network node 820 indicates that it supports bands "n1,n2,n3,n4,n5,n6,n7,n8,n256,n260" (for CA use, for example), bands "n1,n2,n8" and "n4,n7,n256" only for synchronous DC deployments, and band "n3,n5,n260" for asynchronous DC deployments. In response, UE810 reports that it supports band combination "n1,n2" for CA but not for DC, and band combinations "n1,n2,n8" and "n2,n7,n256" for DC (and CA). Since band combination "n1,n2" is not supported for DC, UE810 does not report carrier grouping information for this band combination. In contrast, since the band combinations "n1,n2,n8" and "n2,n7,n256" are supported for DC, the UE810 reports their grouping information. This corresponds to positive carrier grouping information. Alternatively, the UE810 reports that the band combination "n3,n5,n260" is not supported for DC (in this case, the network can assume that the band combinations "n1,n2,n8" and "n2,n7,n256" are supported for DC). Here, the UE810 can simply identify the band combination "n3,n5,n260" which has the attribute of not being supported for DC. Or, the UE810 can include the corresponding part of the carrier grouping information (e.g., the variant of the band combination "n3,n5,n260").

[0093] In response, network node 820 can store UE capability information (including reported carrier aggregation information) in the network (e.g., in the core network). Network node 820 can also configure the MCG and SCG for UE 810 based on the reported carrier aggregation information. For example, network node 820 may determine the supported variants associated with the "n4, n256" band combination and configure a set of carriers from there within the MCG and SCG for synchronous dual connectivity.

[0094] Figure 9 shows another example of sequence diagram 900 illustrating signaling between UE910 and network node 920 for reporting UE capability regarding carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE910 and network node 920 are examples of UE310 and network node 320 in Figure 3, respectively. Compared to sequence diagrams 400-700, the reported UE capability information indicates UE constraints and / or UE requirements. UE constraints and / or UE requirements can be reported in addition to, or instead of, the carrier configuration information (e.g., positive capability information) described with respect to sequence diagrams 400-700. Typically, UE constraint information and UE requirement information are each a type of carrier grouping information. In a sense, constraints can be the negative version of requirements. Here, UE910 indicates some constraint(s) on grouping a set of carriers from a set of bands into a cell group, rather than indicating what it can or cannot support. If a constraint is violated, the UE920 will be unable to support dual connectivity. For example, carrier grouping information indicates a UE constraint on grouping a first carrier from a band into a cell group (MCG or SCG). This UE constraint may indicate that the UE910 cannot support grouping a first carrier from a first band into a cell group, along with a second carrier from a second band within the band. Alternatively, the UE constraint may indicate that the UE can support grouping the first carrier into a cell group without grouping the second carrier into a cell group. Similarly, the UE910 may indicate several requirements regarding grouping sets of carriers from a set of bands into the same or different cell groups. If these requirements are not met, the UE910 will be unable to support dual connectivity. For example, a UE requirement might be to group several carriers from a band into a cell group.Alternatively, the UE requirement indicates that UE910 can support grouping the first carrier from the first band within a cell group only if the second carrier from the second band within the band is also grouped within the cell group.

[0095] Therefore, sequence diagram 900 is an example of a technique in which the UE910 may not support a particular band within a particular cell group. For example, if "NR band n1" (e.g., at least one carrier from it) is present in a cell group, then "NR band n2" (e.g., at least one carrier from it) must not be in the same cell group. Or, "NR band n3" (e.g., at least one carrier from it) must be in the same cell group as "NR band n1" (e.g., at least one carrier from it). The UE910 should be able to reduce signaling overhead simply by reporting such constraints and / or requirements. As part of the UE capability information, the UE910 includes a set of associations (e.g., constraints and / or requirements) related to a particular band, causing the network to assume that the UE910 will support the assignment insofar as the associations are valid in the assignment of carriers to the cell group.

[0096] In one example, sequence diagram 900 includes network node 920 sending a UE capability query to UE910, and UE910 responding with UE capability information. The UE capability query is associated with UE910's support for carrier grouping for dual connectivity. This query may be similar to any of the UE capability queries described in relation to sequence diagrams 400-700. In the example of Figure 9, the UE capability query is similar to that in sequence diagram 700, where network node 910 explicitly indicates the bands for synchronous and asynchronous dual connectivity. From this query, UE920 can determine the band combinations that UE920 supports for CA, a subset of these band combinations that UE920 supports for DC, and, where applicable, a division of this subset between the band combinations that UE910 supports for synchronous DC and the band combinations that UE910 supports for asynchronous DC. UE910 can report this positive capability. In addition, or instead, the UE910 can determine UE constraints and / or UE requirements. For example, for a subset of band combinations that the UE910 supports for DC (or, more specifically, for synchronous and asynchronous DCs), the UE910 may, from its data structure, determine that some bands should not be grouped together within one or more cell groups, thereby forming one or more UE constraints, and determine that some bands should be grouped together, thereby forming one or more UE requirements. The UE910 may then include relevant information regarding its decisions in its UE capability information.

[0097] For illustrative purposes, consider the following example. In a UE capability query, network node 920 indicates that it supports bands "n1,n2,n3,n4,n5,n6,n7,n8,n256,n260" (for CA use, for example), bands "n1,n2,n8" and "n4,n7,n256" only for synchronous DC deployments, and band "n3,n5,n260" for asynchronous DC deployments. In response, UE910 reports that it supports band combination "n1,n2" for CA but not for DC, and band combinations "n1,n2,n3" and "n1,n2,n5" for DC (and CA). Since band combination "n1,n2" is not supported for DC, UE910 does not report carrier grouping information for this band combination. UE910 also examines the variants for the supported bad combinations "n1,n2,n8" and "n2,n7,n256" for DC and determines that the variants indicate that "NR band n1" and "NR band n2" (or carriers from them) must be grouped within the same cell group (e.g., MCG or SCG, or one of them, depending on the support information stored in the data structure). Therefore, UE910 generates a UE requirement that "NR band n1" and "NR band n2" (or carriers from them) must be grouped within the same cell group. Similarly, UE910 determines that "NR band n3" and "NR band n5" must not be grouped within the same cell group. Therefore, UE910 generates a UE constraint that "NR band n3" and "NR band n5" (or carriers from them) must not be grouped within the same cell group. UE910 then indicates the UE constraint and UE requirement within the carrier grouping information included in the UE capability information.

[0098] In response, network node 920 can store UE capability information (including reported carrier aggregation information) in the network (for example, in the core network). Network node 920 can also configure MCG and SCG for UE 910 based on the reported carrier aggregation information. For example, network node 920 may configure a set of carriers from "NR band n1" and "NR band n2" within the MCG or SCG for synchronous dual connectivity.

[0099] Figure 10 shows yet another example of sequence diagram 1000 showing signaling between UE 1010 and network node 1020 for reporting UE capability with respect to carrier grouping, according to several embodiments. In one example, the signaling is RRC signaling exchanged as part of the capability transfer procedure during registration, as described in relation to Figure 3. UE 1010 and network node 1020 are examples of UE 310 and network node 320 in Figure 3, respectively. Compared to sequence diagrams 400-900, the reported UE capability information includes a combination of positive capability information, negative capability information, UE constraint information, and / or UE requirements information. Here, flexibility is achieved so that the network can be queried at any level of granularity, and accordingly UE 1010 can respond with the appropriate level of capability information. Therefore, sequence diagram 1000 is an example of a technique in which the network may choose to request UE 1010 to send a combination of carrier grouping requests, and UE 1010 may choose to provide an appropriate level of capability information (e.g., synchronous carrier grouping with UE constraints, asynchronous carrier grouping without other UE constraints, or enumerating only the actual supported carrier groupings).

[0100] For illustrative purposes, consider the following example. In a UE capability query, network node 1020 indicates that it supports bands "n1,n2,n3,n4,n5,n6,n7,n8,n256,n260" (for CA use, for example), bands "n1,n2,n8" and "n4,n7,n256" only for synchronous DC deployments, and band "n3,n5,n260" for asynchronous DC deployments. A UE capability query may also indicate, but is not required, the type(s) of carrier grouping information to be included in the response (e.g., positive capability information, negative capability information, and / or UE constraint information). If not explicitly indicated in the UE capability query, UE1010 may select a specific type based on default settings or pre-programmed logic (e.g., prioritization logic, logic to determine which type(s) provides the most information with the smallest possible data size). In the example in Figure 10, UE1010 reports that it supports the band combination "n1,n2" for CA rather than DC, the band combinations "n1,n2,n8" and "n4,n7,n256" for synchronous DC, and the band combination "n3,n5,260" for asynchronous DC, along with UE constraints that "NR band n3" and "NR band n5" must not be grouped into MCG, and "N band n1" and "NR band n2" can only be assigned to SCG.

[0101] In response, network node 1020 can store UE capability information (including reported carrier aggregation information) in the network (for example, in the core network). Network node 1020 can also configure MCG and SCG for UE 1010 based on the reported carrier aggregation information. For example, network node 1020 may configure a set of carriers from "NR band n1" and "NR band n2" in the SCG for synchronous DC, and a set of carriers from "NR band n1" and "NR band n8" in the MCG.

[0102] Figure 11 shows an example of the operational flow / algorithm structure 1100 of network nodes constituting carrier grouping according to several embodiments. Network nodes can belong to a network and can be, for example, gNB108, eNB112, or any of network nodes 320-1020, gNB1500, or their components, such as processor 1504, different types of base stations, or wireless network cores (e.g., core network 330). Network nodes can constitute MCG and SCG for UEs supporting dual connectivity.

[0103] The operation flow / algorithm structure 1100 may include determining in 1102 that UE capability information associated with a band combination for a UE is unavailable from the network. For example, this determination may be made as part of a capability transfer procedure during the registration of a UE to the network and may include queries on the core network.

[0104] The operational flow / algorithm structure 1100 may include a UE capability query associated with the UE's support for carrier grouping for dual connectivity, as described in 1104. In one example, this UE capability query is sent in response to a determination that UE capability information is unavailable and may be sent via RRC signaling as part of the capability transfer procedure during UE registration. Furthermore, the UE capability query may include various levels of granularity and / or implicitly or explicitly request the UE to provide its carrier grouping information, as described herein in relation to Figures 4-7.

[0105] The operational flow / algorithm structure 1100 may, in 1106, in response to a UE capability query, include indicating the UE's support for a band combination for dual connectivity and receiving UE capability information from the UE, which includes carrier grouping information relating to the UE's support for grouping carriers of the band combination within cell groups. For example, the UE capability information may indicate supported band combinations for CA, a subset supported for DC, and positive capability information, negative capability information, UE requirement information, and / or UE constraint information relating to this subset, as described herein in relation to Figures 4 to 10.

[0106] The operation flow / algorithm structure 1100 may include configuring cell groups for UEs based on UE capability information in 1108. For example, a network node is an MN and allocates radio resources for MCG using carriers from band combinations supported by the UE. The network node can also notify another network node to configure itself as an SN for the UE according to the band combinations supported by the UE for SCG. The network node can also provide information about MCGs and SCGs that it can provide to the UE.

[0107] Figure 12 shows an example of an operational flow / algorithm structure for a UE that reports its UE capability regarding carrier grouping, according to several embodiments. The UE may implement the operational flow / algorithm structure 600 to determine and use a UE that may be, for example, UE104, any of UE210-1010, UE1400, or their components, such as processor 1404. The UE may support dual connectivity and connect to network nodes in a network that can constitute an MCG and SCG for the UE.

[0108] The operational flow / algorithm structure 1200 may include receiving a UE capability query from a network node in 1202, which is associated with the UE's support for carrier grouping for dual connectivity. In one example, this UE capability query is sent as part of the capability transfer procedure during UE registration. Furthermore, the UE capability query may include various levels of granularity and / or implicitly or explicitly request the UE to provide its carrier grouping information, as described herein in relation to Figures 4-7.

[0109] The operational flow / algorithm structure 1200 may include determining the band combinations that the UE supports for dual connectivity in 1204. For example, parameters from the UE capability query can be used as filters in a lookup of a data structure pre-stored in the UE, which associates, for each band combination supported by the UE, the variants of the bands belonging to the band combination and how these variants can be assigned within the MCG or SCG.

[0110] The operational flow / algorithm structure 1200 may include determining carrier grouping information in 1206 regarding UE support for grouping carriers of a band combination into cell groups. For example, carrier grouping is the result of a lookup, as described herein in relation to Figures 4 to 10, and may include positive capability information, negative capability information, and / or UE constraint information related to this subset.

[0111] The operation flow / algorithm structure 1200 may include, in 1208, indicating UE support for a band combination for dual connectivity in response to a UE capability query, and transmitting UE capability information, including carrier grouping information, to the network node. For example, the UE capability information may indicate supported band combinations for CA, a subset supported for DC, and positive capability information, negative capability information, UE requirement information, and / or UE constraint information related to this subset, as described herein in relation to Figures 4 to 10.

[0112] The operation flow / algorithm structure 1200 may include receiving another UE capability query from another network node (e.g., on another network) at 1210, which is associated with the UE's support for dual connectivity rather than carrier grouping for dual connectivity. For example, this UE capability query may be received when the UE roams to another network and participates in another capability transfer procedure during its registration to the other network. Here, the UE capability query does not have to implicitly or explicitly require the UE to provide its carrier grouping information (e.g., because the network does not support the DC or already has this information about the UE).

[0113] The operational flow / algorithm structure 1200 may include, in 1212, in response to another UE capability query, indicating UE support for band combinations for dual connectivity and sending another UE capability information, excluding carrier grouping information, to another network node. For example, the UE capability information may indicate supported band combinations for CA and a subset supported for DC, but may include either positive capability information, negative capability information, UE requirement information, or UE constraint information.

[0114] Figure 13 shows a receiving component 1300 of the UE 104 according to several embodiments. The receiving component 1300 may include an antenna panel 1304 containing several antenna elements. Panel 1304 is shown with four antenna elements, but other embodiments may include other numbers.

[0115] The antenna panel 1304 may be coupled with an analog beamforming (BF) component, which may include several phase shifters 1308(1) to 1308(4). The phase shifters 1308(1) to 1308(4) may be coupled with a radio frequency (RF) chain 1312. The RF chain 1312 may amplify the received analog RF signal, downconvert the RF signal to baseband, and convert the analog baseband signal into a digital baseband signal that can be provided to a baseband processor for further processing.

[0116] In various embodiments, a control circuit configuration that may reside within the baseband processor may provide phase shifters 1308(1) to 1308(4) with BF weights (e.g., W1 to W4) that can represent phase shift values ​​in order to provide a received beam at antenna panel 1304. These BF weights may be determined based on channel-based beamforming.

[0117] Figure 14 shows UE1400 according to several embodiments. UE1400 may be similar to UE104 in Figure 1 and substantially interchangeable.

[0118] Similar to what is described above with respect to UE104, UE1400 can be any mobile or non-mobile computing device such as a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter or actuator, etc.), video surveillance / monitoring device (e.g., camera or video camera, etc.), wearable device, relaxation IoT device, etc. In some embodiments, UE may be a RedCap UE or an NR-Light UE.

[0119] The UE1400 may include a processor 1404, an RF interface circuit configuration 1408, memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit configuration 1422, a Power Management Integrated Circuit (PMIC) 1424, and a battery 1428. The components of the UE1400 may be implemented as an integrated circuit (IC), a part thereof, individual electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram in Figure 14 is intended to show a high-level diagram of some of the components of the UE1400. However, some of the components shown may be omitted, additional components may be shown, and the components shown may be arranged differently in other implementations.

[0120] The components of the UE1400 may be coupled to various other components via one or more interconnectors 1432, and one or more interconnectors may represent any kind of interface, input / output section, (local, system, or expansion) bus, transmission line, trace, optical connection, etc., that enables various circuit elements (on common or different chips or chipsets) to interact with each other.

[0121] The processor 1404 may include, for example, a baseband processor circuit configuration (BaseBand, BB) 1404A, a central processing unit circuit configuration (CPU) 1404B, and a graphics processing unit circuit configuration (Graphics Processor Unit, GPU) 1404C. The processor 1404 may include any type of circuit configuration or processor circuit configuration that causes the UE 1400 to perform the operations described herein by executing or otherwise operating computer executable instructions such as program code, software modules, or functional processes from memory / storage 1412.

[0122] In some embodiments, the baseband processor circuit configuration 1404A may access the communication protocol stack 1436 in the memory / storage 1412 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit configuration 1404A may access the communication protocol stack to perform user plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer, and control plane functions in the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer "NAS" layer. In some embodiments, the operation of the PHY layer may be performed by components of the RF interface circuit configuration 1408 in addition to / instead of.

[0123] The baseband processor circuit configuration 1404A can generate or process baseband signals or waveforms that carry information within a 3GPP-compliant network. In some embodiments, waveforms for noise reduction (NR) can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0124] The baseband processor circuit configuration 1404A can also access group information 1424 from memory / storage 1412 to determine a search space group to which several PDCCH repetitions may be transmitted.

[0125] The memory / storage 1412 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located within the processor 1404 itself (e.g., L1 and L2 caches), while other memory / storage 1412 may be outside the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include, but is not limited to, any suitable volatile or non-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0126] The RF interface circuit configuration 1408 may include a transceiver circuit configuration and a radio frequency front module (RFEM), thereby enabling the UE 1400 to communicate with other devices via a radio access network. The RF interface circuit configuration 1408 may include various elements arranged in the transmit or receive path. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuit configurations, control circuit configurations, etc.

[0127] In the receiving path, the RFEM receives the radiated signal from the air interface via antenna 1424 and may proceed to filtering and amplification of the signal (using a low-noise amplifier). The signal may be supplied to the receiver of the transceiver, which downconverts the RF signal into a baseband signal provided to the baseband processor of processor 1404.

[0128] In the transmission path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal using a power amplifier before the signal is radiated across the air interface via antenna 1424.

[0129] In various embodiments, the RF interface circuit configuration 1408 may be configured to transmit and receive signals in accordance with NR access technology.

[0130] Antenna 1424 may comprise several antenna elements, each converting electrical signals into radio waves for propagation through the air, and converting received radio waves into electrical signals. The antenna elements may be arranged on one or more antenna panels. Antenna 1424 may have antenna panels that are omnidirectional, directional, or a combination thereof, enabling beamforming and multi-input multi-output communication. Antenna 1424 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1424 may have one or more panels designed for specific frequency bands, including bands within FR1 or FR2.

[0131] The user interface circuit configuration 1416 includes various input / output (I / O) devices designed to enable user interaction with the UE1400. The user interface 1416 includes an input device circuit configuration and an output device circuit configuration. The input device circuit configuration includes, among other things, any physical or virtual means for receiving input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. The output device circuit configuration includes any physical or virtual means for displaying or otherwise transmitting information, such as sensor readings, actuator positions (one or more), or other similar information. The output device circuit configuration may include, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators such as light-emitting diodes (LEDs) and multi-character visual outputs) having outputs such as characters, graphics, and multimedia objects generated or created from the operation of the UE1400, or any number or combination of audio or visual displays including more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.).

[0132] Sensor 1420 may include devices, modules, or subsystems intended to detect events or changes in its environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular, inertial measurement units including accelerometers, gyroscopes, or magnetometers; micro-electromechanical systems or nano-electromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image acquisition devices (e.g., cameras or apertures without lenses); light detection and distance measurement sensors; proximity sensors (e.g., infrared detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices.

[0133] The driver circuit configuration 1422 may include software and hardware elements that operate to control specific devices that are built into, attached to, or otherwise communicatively coupled to the UE1400. The driver circuit configuration 1422 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE1400. For example, the driver circuit configuration 1422 may include a display driver that enables controllable access to a display device, a touchscreen driver that enables controllable access to a touchscreen interface, a sensor driver that obtains sensor readings of the sensor circuit configuration 1420 and enables controllable access to the sensor circuit configuration 1420, a driver that obtains the actuator position of an electromechanical component or enables controllable access to an electromechanical component, a camera driver that enables controllable access to an embedded image capture device, and an audio driver that enables controllable access to one or more audio devices.

[0134] The PMIC1424 can manage the power supplied to various components of the UE1400. In particular, with respect to the processor 1404, the PMIC1424 can control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0135] In some embodiments, the PMIC1424 controls, or may otherwise be part of, various power-saving mechanisms of the UE1400. For example, if the platform UE is in the RRC_CONNECTED state, still connected to the RAN node because it is expected to receive traffic soon, after a period of inactivity, the platform UE may enter a state known as Discontinuous Reception Mode (DRX). During this state, the UE1400 may power down at short intervals, thereby saving power. If there is no data traffic activity for an extended period, the UE1400 may transition to the RRC_Idle state, disconnecting from the network and not performing actions such as channel quality feedback or handover. The UE1400 enters a very low power state and performs paging, periodically waking up again to listen to the network and then powering down again. The UE1400 may not be able to receive data in this state. To receive data, it needs to transition back to the original RRC_Connected state. In further power-saving modes, devices may be allowed to be unavailable from the network for longer periods than the paging interval (ranging from a few seconds to several hours). During this time, the device may be completely unable to reach the network and may be completely powered off. Any data transmitted during this time will experience significant delays, but these delays are considered acceptable.

[0136] Battery 1428 may supply power to UE1400, but in some examples, UE1400 may be installed in a fixed location or have a power source connected to a power grid. Battery 1428 may be a lithium-ion battery, a zinc-air battery, an aluminum-air battery, a lithium-air battery, or the like. In some implementations, such as vehicle-based applications, battery 1428 may be a typical automotive lead-acid battery.

[0137] Figure 15 shows gNB1500 according to several embodiments. gNB node 1500 is similar to gNB108 and may be substantially interchangeable. Base stations such as base station 112 may have the same or similar components as gNB1500.

[0138] The gNB1500 may include a processor 1504, an RF interface circuit configuration 1508, a Core Network (CN) interface circuit configuration 1512, and a memory / storage circuit configuration 1516.

[0139] The components of the gNB1500 may be coupled to various other components via one or more interconnection parts 1528.

[0140] The processor 1504, RF interface circuit configuration 1508, memory / storage circuit configuration 1516 (including the communication protocol stack 1510), antenna 1524, and interconnect 1528 may be similar to elements with similar names that are illustrated and described with respect to Figure 13.

[0141] The CN interface circuit configuration 1512 is a core network, for example, a 5th generation core network "5 thConnectivity to the Generation Core network, 5GC, can be provided using a 5GC-compliant network interface protocol such as the Carrier Ethernet protocol or some other suitable protocol. Network connectivity can be provided to or from the gNB1500 via optical fiber or wireless backhaul. The CN interface circuit configuration 1512 may include one or more dedicated processors or FPGAs for communication using one or more of the protocols described above. In some implementations, the CN interface circuit configuration 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0142] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0143] For one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, or methods as described in the following exemplary sections. For example, a baseband circuit configuration described in relation to one or more of the aforementioned drawings may be configured to operate according to one or more of the examples described below. As another example, a circuit configuration associated with a UE, base station, network element, etc., as described in relation to one or more of the aforementioned drawings, may be configured in the embodiment section to operate according to one or more of the examples described below.

[0144] Examples Further exemplary embodiments are provided in the following sections.

[0145] Example 1 includes a method, which is performed by a user device (UE). The method includes receiving a UE capability query from a network node associated with the UE's support for carrier grouping for dual connectivity; determining the band combinations that the UE supports for dual connectivity; determining carrier grouping information regarding the UE's support for grouping carriers of the band combinations within cell groups; and, in response to the UE capability query, transmitting UE capability information to the network node indicating the UE's support for the band combinations for dual connectivity and including carrier grouping information regarding dual connectivity.

[0146] Embodiment 2 includes a method, which is performed by a network node. The method includes sending a UE capability query to a user device (UE) relating to the UE's support for carrier grouping for dual connectivity; receiving UE capability information from the UE in response to the UE capability query, which includes carrier grouping information relating to the UE's support for band combinations for dual connectivity and for grouping carriers of band combinations within cell groups for dual connectivity; and configuring cell groups for dual connectivity for the UE based on the UE capability information.

[0147] Example 3 involves one of the methods described in Examples 1 to 2 above, and the UE capability query indicates that the network node supports grouping multiple carriers from different frequency ranges within the same cell group for dual connectivity.

[0148] Example 4 involves one of the methods described in Examples 1 through 3 above, where the UE capability query indicates that the network node supports a set of band combinations for dual connectivity, and the set includes band combinations.

[0149] Example 5 involves one of the methods described in Examples 1 through 4 above, where the UE capability query indicates that the network node supports a set of band combinations for a synchronous deployment of dual connectivity, and the set includes band combinations.

[0150] Example 6 involves one of the methods described in Examples 1 through 5 above, where the UE capability query indicates that the network node supports a set of band combinations for asynchronous deployment of dual connectivity, and the set includes band combinations.

[0151] Example 7 includes one of the methods described in Examples 1 through 6 above, where the UE capability information indicates multiple bands in different frequency ranges that form a band combination, and the carrier grouping information indicates that the UE supports grouping carriers from different frequency ranges within a cell group for dual connectivity.

[0152] Example 8 includes one of the methods described in Examples 1 to 7 above, wherein the second capability information is configured to indicate that the UE can support a third measurement gap configuration only if the first capability information is configured to indicate that the UE can support a first measurement gap configuration and a second measurement gap configuration, the UE capability information indicates multiple bands of the band combination, and the carrier grouping information indicates that the UE supports grouping a first carrier in a first band of multiple bands into a master cell group (MCG) and grouping a second carrier in a second band of multiple bands into a secondary cell group (SCG).

[0153] Example 9 includes one of the methods described in Examples 1 through 8 above, where the UE capability information indicates multiple bands from the band combination, and the carrier grouping information indicates that the UE cannot support grouping a first carrier from a first subset of multiple bands within a cell group for dual connectivity.

[0154] Example 10 includes one of the methods described in Examples 1 through 9 above, where UE capability information indicates multiple bands of the band combination, and carrier grouping information indicates UE constraints on grouping the first carrier from multiple bands into a cell group for dual connectivity.

[0155] Example 11 includes one of the methods described in Examples 1 through 10 above, wherein the UE capability information indicates multiple bands of the band combination, and the carrier grouping information indicates that the UE cannot support grouping a first carrier from a first band of multiple bands within a cell group for dual connectivity, along with a second carrier from a second band of multiple bands.

[0156] Example 12 includes the method of Example 11 and further demonstrates that the carrier grouping information allows the UE to support grouping the first carrier within a cell group without having to group the second carrier within the cell group for dual connectivity.

[0157] Example 13 includes one of the methods described in Examples 1 through 12 above, where UE capability information indicates multiple bands of the band combination, and carrier grouping information indicates the UE requirement for grouping a first carrier from multiple bands into a cell group for dual connectivity.

[0158] Example 14 includes one of the methods described in Examples 1 to 13 above, wherein the UE capability information indicates multiple bands of the band combination, and the carrier grouping information indicates that the UE can support grouping a first carrier from a first band of multiple bands into a cell group only when a second carrier from a second band of multiple bands is also grouped into a cell group for dual connectivity.

[0159] Example 15 includes one of the methods described in Examples 1 through 14 above, wherein the UE capability information indicates multiple bands of the band combination, the carrier grouping information indicates UE constraints for grouping a first carrier from multiple bands into a cell group for dual connectivity, and the carrier grouping information further indicates UE requirements for grouping a second carrier from multiple bands into a cell group for dual connectivity.

[0160] Example 16 includes one of the methods described in Examples 1 to 15 above, the method further including receiving another UE capability query from another network node that is associated with UE support for dual connectivity rather than carrier grouping for dual connectivity, and in response to the other UE capability query, sending another UE capability information to the other network node indicating UE support for band combinations for dual connectivity and excluding carrier grouping information.

[0161] Example 17 includes one of the methods described in Examples 1 through 16 above, where the UE capability query indicates that the network node supports grouping multiple carriers from different frequency ranges within a cell group, and the carrier grouping information indicates that the UE supports grouping multiple carriers from different frequency ranges within a cell group for dual connectivity.

[0162] Example 18 includes one of the methods described in Examples 1 through 17 above, wherein the UE capability query indicates that a network node supports a set of band combinations for dual connectivity, the set includes band combinations, and the carrier grouping information indicates that the UE supports grouping a first carrier in a first band from a band combination into a master cell group (MCG) and a second carrier in a second band from a band combination into a secondary cell group (SCG).

[0163] Example 19 includes one of the methods described in Examples 1 through 18 above, wherein the UE capability query indicates that the network node supports a dual connectivity synchronous deployment or a set of band combinations for a synchronous deployment, the set includes band combinations, and the carrier grouping information indicates that the UE does not support a synchronous deployment or grouping the first carrier from the band combinations into a cell group for a synchronous deployment.

[0164] Example 20 includes a UE that includes means for performing one or more elements of the methods described or related to any of Examples 1 to 19.

[0165] Example 21 includes one or more non-temporary computer-readable media containing instructions that, when executed by one or more processors of the UE, cause the UE to execute one or more elements of the methods described or related to any one of Examples 1 and 3 through 19.

[0166] Example 22 includes a UE that includes logic, modules, or circuit configurations for performing one or more elements of the methods described or related to any one of Examples 3 through 19.

[0167] Example 23 includes a UE comprising one or more processors and one or more computer-readable media containing instructions that, when executed by one or more processors, cause one or more processors to execute one or more elements of any one of Examples 1 and 3 to 19.

[0168] Example 24 includes a system that includes means for performing one or more elements of the methods described in or relating to any one of Examples 1 and 3 through 19.

[0169] Example 25 includes a network node that includes means for performing one or more elements of the methods described or related to any one of Examples 2 to 15 and Examples 16 to 19.

[0170] Example 26 includes one or more non-temporary computer-readable media containing instructions that, when executed by one or more processors of a network node, cause the network node to execute one or more elements of the methods described or related to any one of Examples 2 to 15 and Examples 16 to 19.

[0171] Example 27 includes a network node that includes logic, modules, or circuit configurations for performing one or more elements of the methods described or related to any one of Examples 2-15 and Examples 16-19.

[0172] Example 28 includes a network node comprising one or more processors and one or more computer-readable media containing instructions that, when executed by one or more processors, cause one or more processors to execute one or more elements of any one of Examples 2 to 15 and Examples 16 to 19.

[0173] Example 29 includes a system that includes means for performing one or more elements of the methods described or related to any one of Examples 2 to 15 and Examples 16 to 19.

[0174] Any of the above examples may be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementations are illustrative and illustrative, but are not intended to be exhaustive or to strictly limit the scope of embodiments to those disclosed. Modifications and variations are possible based on the above teachings or can be learned from the practice of various embodiments.

[0175] Although the embodiments described above have been explained in considerable detail, many variations and modifications will become apparent to those skilled in the art upon a full understanding of the above disclosure. The following claims are intended to be construed as encompassing all such variations and modifications.

Claims

1. It is a method, Sending a UE capability query to the user equipment (UE) including instructions for cell grouping for dual connectivity, wherein the cell grouping includes a first band list for the master cell group (MCG) and a second band list for the secondary cell group (SCG), A method comprising receiving from the UE, in response to the UE capability query, UE capability information indicating support for the band combination for dual connectivity, and cell grouping information relating to cells for the band combination and cells supported by the UE for dual connectivity, wherein the cell grouping information is included in the UE capability information only if the UE capability query includes the instruction, and the cell grouping information includes an identifier for the cell grouping among a plurality of cell groupings supported by the network, the identifier indicating at least one of the plurality of cell groupings in which the UE supports a grouping of at least one MCG band of the MCG and at least one SCG band of the SCG.

2. The method according to claim 1, further comprising communicating with the UE based on the UE capability information.

3. The method according to claim 2, wherein the communication is performed using a cell selected from cells belonging to the band combination and supported by the UE for dual connectivity.

4. The method according to any one of claims 1 to 3, wherein the UE capability query indicates that the network supports grouping bands within the cell group for dual connectivity.

5. The method according to claim 4, wherein the cell group is the MCG or the SCG.

6. The method according to any one of claims 1 to 3, wherein the UE capability query indicates that the network supports a set of band combinations for the dual connectivity, and the set includes the band combinations.

7. It is a method, Processing user equipment (UE) capability queries received from the network, wherein the UE capability query includes instructions for cell grouping for dual connectivity, the cell grouping corresponds to the bands available by the network, and includes a first band list for the master cell group (MCG) and a second band list for the secondary cell group (SCG). A method comprising, in response to the UE capability query, causing the network to transmit UE capability information indicating support for a band combination grouped into a cell group, wherein the support is indicated in the UE capability information based on the UE capability query including the instruction, the support includes a cell group identifier among a plurality of cell groupings supported by the network, the identifier indicates at least one of the plurality of cell groupings for which the UE supports a grouping of at least one MCG band of the MCG and at least one SCG band of the SCG.

8. The method according to claim 7, further comprising communicating with the network based on the UE capability information.

9. The method according to claim 7 or 8, wherein the UE capability information is transmitted only if the UE capability inquiry includes the instruction.

10. The method according to claim 7 or 8, wherein the UE capability information indicates dual connectivity support for band combinations corresponding to the cell grouping.

11. The method according to claim 7 or 8, wherein the UE capability query indicates the band associated with the cell group.

12. The method according to claim 11, wherein the UE capability information corresponds to two or more of the bands and indicates the band combinations supported for the cell group.

13. The method according to claim 7 or 8, wherein the UE capability information indicates a plurality of bands that form the band combination and belong to different frequency ranges.

14. The method according to claim 7 or 8, wherein the UE capability information indicates a plurality of bands of the band combination.

15. The method according to claim 14, wherein the UE capability information further indicates support for a first carrier in a first band of the plurality of bands grouped in the MCG and a second carrier in a second band of the plurality of bands grouped in the SCG.

16. The method according to claim 14, wherein the UE capability information indicates a plurality of bands of the band combination, and the UE capability information further indicates that there is no support for a first carrier from a first subset of the plurality of bands grouped in the cell group for the dual connectivity.

17. It is a device, It has a processing circuit, and the processing circuit is The system processes user equipment (UE) capability queries received from the network, where the UE capability query includes instructions for cell grouping for dual connectivity, and the cell grouping corresponds to the bands available to the network, and includes a first band list for the master cell group (MCG) and a second band list for the secondary cell group (SCG). A device configured to, in response to the aforementioned UE capability query, cause the network to transmit UE capability information indicating support for a combination of bands grouped into a cell group, wherein, based on the inclusion of the instruction in the UE capability query, the support is indicated in the UE capability information, the support includes an identifier for a cell grouping among a plurality of cell groupings supported by the network, the identifier indicates at least one of the plurality of cell groupings in which the UE supports a grouping of at least one MCG band of the MCG and at least one SCG band of the SCG.

18. The apparatus according to claim 17, wherein the UE capability query indicates that the network supports a set of bands for the dual connectivity, the set of bands includes a first band and a second band belonging to the band combination.

19. The apparatus according to claim 18, wherein the UE capability query indicates that the network supports the set of bands associated with the MCG or the SCG.

Images