Method, device and system for capability coordination in dual connectivity

Abstract

Methods, systems, and devices are described for user equipment (UE) capability coordination in dual connectivity (DC). In one embodiment, a method includes transmitting, by a user equipment (UE), UE assistance information including UE temporary capability constraints to a first network, the UE capability constraints indicating one or more constraint dimensions to the first network. Another method includes receiving, by a first network from a UE, UE assistance information including UE temporary capability constraints, the UE capability constraints indicating one or more constraint dimensions to the first network.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication. In particular, the present disclosure relates to methods, devices, and systems for user equipment (UE) capability coordination in dual connectivity (DC). Background Art

[0002] Wireless communication technologies are moving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). The new generation of networks is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet the needs of different industries and users.

[0003] For fifth-generation (5G) mobile communication technologies, user equipment (UE) (e.g., a smartphone) may be temporarily constrained in its communication capabilities. For example, when a UE operates in a dual-active state with two networks, the UE may have temporary UE capability constraints for connecting to these two networks. There are various challenges / issues associated with such a situation, e.g., how the UE indicates the temporary UE capability constraints to one or both of the two networks.

[0004] The present disclosure describes various embodiments for capability coordination in dual connectivity, solves at least one of the problems / issues described in the present disclosure, and improves the performance of wireless communication. Summary of the Invention

[0005] This document relates to methods, systems, and devices for wireless communication, and more particularly, to methods, devices, and systems for coordinating user equipment (UE) capabilities in dual connectivity (DC).

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes a user equipment (UE) sending UE assistance information including a UE temporary capability constraint to a first network, the UE capability constraint indicating to the first network one or more restriction dimensions.

[0007] In another embodiment, the present disclosure describes a method for wireless communication. The method includes a first network receiving UE assistance information including a UE temporary capability constraint from a user equipment (UE), the UE capability constraint indicating to the first network one or more restriction dimensions.

[0008] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0009] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0010] In some other embodiments, a computer-readable medium comprising instructions that, when executed by a computer, cause the computer to perform the above method. The computer-readable medium may be referred to as a non-transitory computer-readable medium (CRM) that stores data for a long time, such as a flash drive or a compact disc (CD), or stores data for a short time while powered on, such as a storage device or a random access memory (RAM).

[0011] The above aspects and other aspects and their implementations will be described in more detail in the drawings, the description, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An example of a wireless communication system including more than one network node and one or more user equipments is shown.

[0013] Figure 2 An example of a network node is shown.

[0014] Figure 3 An example of a user equipment is shown.

[0015] Figure 4 An exemplary list of feature set entries for an exemplary embodiment for wireless communication is shown.

[0016] Figure 5 An exemplary general procedure for a provisional capability report for an exemplary embodiment for wireless communication is shown.

[0017] Figure 6A A flowchart of a method for wireless communication is shown.

[0018] Figure 6B A flowchart of another method for wireless communication is shown.

[0019] Figure 7 A schematic diagram of an exemplary embodiment for wireless communication is shown.

[0020] Figure 8A A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0021] Figure 8B A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0022] Figure 9 A schematic diagram of another exemplary embodiment for wireless communication is shown.

[0023] Figure 10A A schematic diagram showing another exemplary embodiment for wireless communication.

[0024] Figure 10B A schematic diagram showing another exemplary embodiment for wireless communication.

[0025] Figure 11A A schematic diagram showing another exemplary embodiment for wireless communication.

[0026] Figure 11B A schematic diagram showing another exemplary embodiment for wireless communication.

[0027] Figure 12A A schematic diagram showing another exemplary embodiment for wireless communication.

[0028] Figure 12B A schematic diagram showing another exemplary embodiment for wireless communication.

[0029] Figure 13A A schematic diagram showing another exemplary embodiment for wireless communication.

[0030] Figure 13B A schematic diagram showing another exemplary embodiment for wireless communication.

[0031] Figure 14 A schematic diagram showing another exemplary embodiment for wireless communication.

[0032] Figure 15A A schematic diagram showing another exemplary embodiment for wireless communication.

[0033] Figure 15B A schematic diagram showing another exemplary embodiment for wireless communication.

[0034] Figure 16 A schematic diagram showing another exemplary embodiment for wireless communication.

[0035] Figure 17A A schematic diagram showing another exemplary embodiment for wireless communication.

[0036] Figure 17B A schematic diagram showing another exemplary embodiment for wireless communication.

[0037] Figure 17C A schematic diagram showing another exemplary embodiment for wireless communication.

[0038] Figure 17D A schematic diagram showing another exemplary embodiment for wireless communication.

[0039] Figure 17E A schematic diagram showing another exemplary embodiment for wireless communication.

[0040] Figure 17F A schematic diagram showing another exemplary embodiment for wireless communication.

[0041] Figure 17G A schematic diagram showing another exemplary embodiment for wireless communication.

[0042] Figure 17H A schematic diagram showing another exemplary embodiment for wireless communication. Detailed Description

[0043] The present disclosure will now be described in detail below with reference to the accompanying drawings that form a part of the present disclosure, and the accompanying drawings illustrate specific examples of the embodiments by way of illustration. However, note that the present disclosure can be embodied in various different forms, and thus, the subject matter covered or claimed is intended to be construed as not limited to any of the embodiments set forth below.

[0044] Throughout the specification and claims, terms may have nuanced meanings that are implied or implicit in the context, which go beyond the explicitly stated meanings. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, it is intended that the claimed subject matter includes combinations of all or part of the exemplary embodiments or implementations.

[0045] In general, terms can be understood, at least in part, from their usage in context. For example, terms such as "and," "or," or "and / or" used herein can include a variety of meanings, which depend, at least in part, on the context in which these terms are used. Generally, "or" if used in connection with a list, such as A, B, or C, can mean A, B, and C, where used in an inclusive sense, as well as A, B, or C, where used in an exclusive sense. Additionally, the terms "one or more" or "at least one" used herein depend, at least in part, on the context and can be used to describe any feature, structure, or characteristic in a singular sense or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as "a," "an," or "the" can also be understood to denote a singular usage or a plural usage, at least in part, depending on the context. Additionally, the terms "based on" or "determined by" can be understood to not necessarily imply a set of exclusive factors and, instead, can allow for additional factors that are not necessarily explicitly described, at least in part, depending on the context.

[0046] The present disclosure describes methods and apparatuses for user equipment (UE) capability coordination in dual connectivity (DC).

[0047] The new generation (NG) mobile communication system is driving the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and radio access network nodes (including but not limited to radio base stations). The new generation network is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet the needs of different industries and users.

[0048] The present disclosure describes various embodiments for user equipment (UE) capability coordination in dual connectivity (DC). In one or more scenarios, a user equipment (UE) can be simultaneously connected to more than one network node. These network nodes can include, for example, one or more radio access network (RAN) nodes and / or one or more core network (CN) nodes. In one implementation, the UE can be simultaneously connected to two network nodes, which can be referred to as a "dual active state," which requires the UE and / or one or more network nodes to coordinate multiple connections in order to provide an efficient system for one or more scenarios.

[0049] A scenario can include that, for a UE with multiple user identity modules (MSIMs) (or multiple universal subscriber identity modules), the UE can be connected to multiple networks simultaneously. In another scenario, a UE with a single SIM can be connected to multiple networks simultaneously. Another scenario can include that a roaming UE can be connected to multiple networks for different slices. In another scenario, as an enhancement to slices, a wireless communication system may need to enable a roaming UE to simultaneously access network slices from more than one visited public land mobile network (VPLMN), which means the UE can be connected to two networks simultaneously, similar to an MSIM. In another scenario, video, imaging, and audio for professional applications (VIAPA) may require a method to enable a UE to receive data services from one network (e.g., a non-public network (NPN)) and simultaneously receive paging and data services from another network (e.g., a public land mobile network (PLMN)), similar to an MSIM.

[0050] When a UE is configured to be connected to multiple networks simultaneously, it may be necessary to coordinate the UE capabilities. In some embodiments with radio access capability signaling (RACS), the UE radio access capabilities can be packaged as predefined or network-defined UE capability IDs.

[0051] In various embodiments, for an MSIM (or MUSIM), the UE can be connected to multiple networks simultaneously for different situations.

[0052] In some embodiments, when the first subscriber identity module (SIM1) is in a connected state, paging reception on the second subscriber identity module (SIM2) can be solved through time-division multiplexing (TDM), such as reserving a scheduling gap for SIM2. Since it is not possible to connect to two networks simultaneously, there may be no cooperation at this time. However, for a dual receive / transmit (RX) UE, this scheme may affect the performance of SIM1 by reserving a scheduling gap within the paging cycle. Another solution for a dual RX UE is to reserve some radio frequency or physical (RF / PHY) resources for paging reception. In some embodiments with a short dual-connection state, SIM1 can be in a connected state, and SIM2 must perform some mobility updates, such as periodic registration, moving to a new registration area, or responding to a paging. The UE may need capability cooperation during this short dual-connection state. In some embodiments with a long dual-connection state, the UE can make a voice call on SIM1 while performing some other data services on SIM2. The UE will need capability cooperation.

[0053] There may be some problems / difficulties that need to be solved. For example, the hardware capabilities of a MSIM (or MUSIM) UE can be shared by more than one SIM. To use the hardware efficiently and economically, the relevant capabilities need to be dynamically divided among more than one SIM. This may lead to temporary hardware conflicts. For example, the UE is connected to one network (Network A), and it will have some capability constraints for another network (Network B). Therefore, when the UE enters the connection state with Network B, the UE needs to indicate the capability constraints to Network B.

[0054] This disclosure describes various embodiments of UE capability coordination in a dual-active state, which solve at least one of the above problems / difficulties, provide solutions, and improve the performance of wireless communication.

[0055] Figure 1 A wireless communication system 100 is shown that includes more than one network node (118 and 119) and one or more user equipment (UE) (110, 111, and 112). In some embodiments, the two network nodes (118 and 119) can be from two different networks or from the same network.

[0056] For fifth-generation mobile communication technology, the UE 110 (e.g., a smart phone) can have a single subscriber identity module (SIM) or multiple subscriber identity modules. When the UE has a single SIM, the UE can be connected to one network node 118, e.g., a radio access network (RAN) node and / or a core network (CN) node, or can be connected to more than one network node (118 and 119), e.g., two RAN nodes and / or two CN nodes. When the UE has a MSIM, the UE can be connected to more than one network node (118 and 119), e.g., two RAN nodes, two CN nodes, and / or one RAN node and one CN node.

[0057] The wireless network nodes (118 and 119) can include network base stations, which can be Node B (NB, e.g., eNB or gNB) in a mobile telecommunications environment. Each of the UEs (110, 111, and / or 112) can communicate wirelessly with the wireless network nodes (118 and / or 119) via one or more wireless channels 115. For example, the first UE 110 can communicate wirelessly with the first network node 118 via a channel including multiple wireless channels during a specific period; during another period or simultaneously, the first UE 110 can communicate wirelessly with the second network node 119 via a channel including multiple radio channels.

[0058] The present disclosure describes various embodiments of user equipment (UE) capability coordination in dual connectivity (DC) for one, some, or all scenarios described in the present disclosure. The present disclosure describes methods, systems, and storage media for how a UE coordinates temporary UE capability constraints (e.g., UE capability constraint information) with one or more networks (or network nodes), and / or how one or more network nodes coordinate temporary UE capability constraints (e.g., UE capability constraint information) with other network nodes and / or the UE.

[0059] Figure 2 An example of an electronic device 200 for implementing a network node or a network base station is shown. The example electronic device 200 may include a wireless transmit / receive (Tx / Rx) circuit 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include a network interface circuit 209 for communicating the base station with other base stations and / or a core network, e.g., optical or wired interconnections, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0060] The electronic device 200 may also include a system circuit 204. The system circuit 204 may include one or more processors 221 and / or a memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured for one or more processors 221 to perform the functions of the network node. The parameters 228 may include parameters for supporting the execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0061] Figure 3 An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, e.g., a smart phone or a mobile communication module installed in a vehicle. The UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a storage device 309. The display circuit may include a user interface 310.

[0062] System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuitry. System circuitry 304 may be implemented, for example, using one or more system-on-chips (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuitry, and other circuitry. System circuitry 304 may be part of the implementation of any desired functionality in the UE 300. In this regard, system circuitry 304 may include, for example, logic that facilitates the decoding and playback of music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, as an example, for Internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic output, voice or face recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of the I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0063] Reference Figure 3 , the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The signals transmitted and received may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and codings. As a specific example, the communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G, and / or further developed standards. However, the techniques described below apply to other wireless communication technologies, regardless of whether they are derived from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0064] Reference Figure 3 As shown in Figure 3 , the system circuit 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to implement the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operation options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that the UE 300 will send or has received via the communication interface 302. In various embodiments, the system power of the UE 300 may be supplied by a power storage device such as a battery or a transformer.

[0065] The present disclosure describes several embodiments that may be implemented, in whole or in part, on the network base stations and / or user equipment described in Figures 2 to 3 below.

[0066] In some embodiments, for MUSIM enhancement, the hardware functions of the MUSIM UE are shared by these SIMs, and to use the hardware efficiently and economically, the relevant functions need to be dynamically split between the two SIMs. This may lead to temporary hardware conflicts. For example, when the UE is connected to Network A and needs to enter the connection state with Network B, it will have some capability constraints for Network A. Therefore, the UE needs to indicate the capability constraints to Network A.

[0067] In some embodiments, in the master node - secondary node (MN - SN) coordination, the capability coordination may be performed as follows: the MN indicates the available band combination (BC) information to the SN (MN -> SN).

[0068] BandCombinationInfoList::=SEQUENCE(SIZE(1..maxBandComb)) OF BandCombinationInfo

[0069] BandCombinationInfo::=SEQUENCE{

[0070] bandCombinationIndex BandCombinationIndex,

[0071] allowedFeatureSetsList SEQUENCE(SIZE

[0072] (1..maxFeatureSetsPerBand)) OF FeatureSetEntryIndex

[0073] }

[0074] selectedBandEntriesMNList SEQUENCE(SIZE(1..maxBandComb)) OF SelectedBandEntriesMN

[0075] SelectedBandEntriesMN ::= SEQUENCE(SIZE

[0076] (1..maxSimultaneousBands)) OF BandEntryIndex

[0077] In the above, MN can indicate to SN regarding the available BCs, the selected band entries and the feature set entries for each BC. For example, referring to Figure 4 , for BC1, there are 3 bands (e.g., Band 1, Band 2, and Band 3), and there are also 3 feature set entries (e.g., FeatureSetEntry 1, FeatureSetEntry 2, and FeatureSetEntry 3) in the corresponding FeatureSetCombination.

[0078] In some embodiments, for BC1, when only FeatureSetEntry 1 and FeatureSetEntry 3 can be used by SN, MN can set allowedFeatureSetList = [0][2] for BC1, indicating FeatureSetEntry 1 and FeatureSetEntry 3.

[0079] In some embodiments, for BC1, when MN selects Band 1 and Band 2, MN will set SelectedBandEntriesMN = [0][1] for BC1, indicating Band 1 and Band 2.

[0080] In some embodiments, from the perspective of a MUSIM UE RF, when it operates in a dual-connectivity state using 2 USIMs, it will be similar to MR-DC, so a similar capability coordination scheme can be considered. For example, the UE indicates the allowed BCs and one or more corresponding feature set entries, and the UE can also indicate the prohibited BCs or prohibited FeatureSets. Through these embodiments, the UE can provide comprehensive capability constraint information to the network.

[0081] In some embodiments, referring to Figure 5, the UE (580) can report auxiliary information on capacity constraints to the network by using a procedure. The UE may include a SIM1 access stratum (AS) 582 and a SIM2 AS 584, which are configured to connect to a SIM1 e / gNB A 692. The procedure may include some or all of the following steps. Step 1, the UE (SIM1 AS) is in a connected state with the SIM 1 e / gNB A via band A. Step 2, the UE needs to enter an active state on band B. Step 3, the UE determines temporary capacity constraints. Step 4, the UE sends UE auxiliary information with the temporary capacity constraints to the SIM 1 e / gNB A. Step 5, the SIM 1 e / gNB A sends a reconfiguration message to the UE. Step 6, the UE sends a reconfiguration complete to the SIM 1 e / gNB A.

[0082] In some embodiments, the UE may indicate the temporary capacity constraints in the UE auxiliary information (UAI), including one or more of the following: allowed / prohibited BC or feature set or maximum multiple-input multiple-output (MIMO) layer, maximum number of CCs as energy saving / overheating, or SCell / SCG release. The temporary capacity constraints include capacity updates, release of cells, and / or (de)activation of configured resources, etc. The UE may indicate such constraints with band combination information.

[0083] In some embodiments, a list of reported band combinations will be present in the UE capability structure, and for each BC, there will be a FeaturesetCombination. For each FeaturesetCombination, there may be one or more feature set combinations. Taking BC1 as an example below (e.g., Figure 4 ), there are 3 feature set combination entries. For example, BC1 -> FeaturesetCombination ID index (or number (No.)).

[0084] In some embodiments, to report the temporary capacity constraints, the UE may indicate at least one of the following BC lists: list of allowed BCs: BCs with corresponding feature set capabilities can be used without any constraints; list of affected BCs: there are some constraints on these BCs, and / or list of prohibited BCs, which are prohibited.

[0085] In some embodiments, for the list of affected BCs, the UE may also indicate the affected feature set combination entries. The feature set combination entries may include at least one of the following: list of allowed feature set combination entries: feature set combination entries with corresponding feature set capabilities can be used without any constraints; list of affected feature set combination entries: there are some constraints on these feature set combination entries; and / or list of prohibited feature set combination entries: these feature set combination entries are prohibited.

[0086] For a non - limiting example, when for BC1, the UE can only support feature set combination entries 1 and 3, the UE can indicate that the prohibited feature set combination entry 2 is entered into the prohibited feature set entry list of BC1, or the UE can indicate to the network that feature set combination entries 1 and 3 are entered into the allowed feature set entry list.

[0087] In various embodiments, methods for solving at least one of the following problems are described. One problem includes how to indicate relevant feature set entries for each BC, especially in cases where only fallback capabilities are supported. Another problem includes how to indicate selected frequency band entries, how to indicate frequency band entries of a second network (Network B), or how to indicate allowed frequency band entries of a first network (Network A). Another problem includes how to indicate capability constraints using an inter - node message (INM).

[0088] Referring to Figure 6A , this disclosure describes embodiments of a method 600 for wireless communication. Method 600 may include step 610 of a user equipment (UE) sending UE assistance information including UE temporary capability constraints to a first network, where the UE capability constraints indicate to the first network one or more constraint dimensions.

[0089] Without limiting this disclosure, the various embodiments described below may use a UE with an MSIM. These embodiments are examples and do not limit this disclosure, which can also be applied to other scenarios where the UE needs to be simultaneously connected to two networks or the UE will be configured to be simultaneously connected to two networks.

[0090] In some implementations, in addition to the implementations or parts or combinations of embodiments described in this disclosure, one or more UE capability constraint dimensions include constraints on each other.

[0091] In some implementations, in addition to the implementations or parts or combinations of embodiments described in this disclosure, the UE also includes multiple universal subscriber identity modules (MUSIMs) corresponding to a first subscription of a first network and a second subscription of a second network.

[0092] In some implementations, in addition to the implementations or parts or combinations of embodiments described in this disclosure, the UE temporary capability constraints further include constraint information at a granularity level; and / or the granularity level includes at least one of the following: per - UE level, per - frequency - band level, per - frequency - band combination (BC) level, per - frequency - band per - BC level, per - feature - set - entry per - frequency - band level, or per - carrier - component per - BC level.

[0093] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to the affected BC list, and / or the second dimension includes a set of parameter restrictions at a granularity level, and / or the set of parameter restrictions includes at least one of the following: maximum multiple-input multiple-output (MIMO) layer, maximum modulation order, or maximum supported bandwidth.

[0094] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the affected BC report further includes a list of feature set entries corresponding to at least one BC or a part thereof in the affected BC list, and / or the list of feature set entries includes at least one of the following: allowed feature set entries, affected feature set entries, or prohibited feature set entries.

[0095] In some embodiments, in addition to a part or combination of the one or more implementations or examples described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to the affected BC list of the UE, and / or the second dimension includes a set of parameter restrictions of the UE; and / or the UE determines the set of supported parameters by: for each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions of the UE.

[0096] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to the affected BC list having a list of feature set entries, and / or the second dimension includes a set of parameter restrictions for each frequency band; and / or the UE determines the set of supported parameters by: for each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions of the frequency band.

[0097] In some embodiments, in addition to a part or combination of the one or more implementations or examples described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to the affected BC list having a list of feature set entries, and / or the second dimension includes a set of parameter restrictions for each BC or a part of each BC in the affected BC list; and / or the UE determines the set of supported parameters by: for each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions for each BC or a part of each BC.

[0098] In some embodiments, in addition to a combination of some or more implementations or embodiments described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to an affected BC list having a list of feature set entries, and / or the second dimension includes a set of parameter restrictions for each frequency band of each BC or a part of each BC in the affected BC list; and / or the UE determines the set of supported parameters by: for each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions for each frequency band of each BC or a part of each BC.

[0099] In some embodiments, in addition to a combination of some or part of the embodiments or examples described in the present disclosure, the affected BC list further includes at least one of the following: an allowed BC or a prohibited BC; and / or each frequency band in the affected BC list is represented by at least one of the following: a band number, an absolute radio frequency channel number (ARFCN) value, or an index, where the index indicates the position of the frequency band in the list of frequency bands in the UE capability request message.

[0100] In some embodiments, in addition to a combination of some or part of the embodiments or examples described in the present disclosure, the UE further indicates at least one of the following to the first network: an indication of at least one selected frequency band entry for the second network, and / or an indication of at least one allowed frequency band entry for the first network.

[0101] Referring to Figure 6B , the present disclosure describes embodiments of a method 650 for wireless communication. The method 650 may include step 660 of receiving, by a first network, UE assistance information including a UE temporary capability constraint from a user equipment (UE), the UE capability constraint indicating one or more constraint dimensions to the first network.

[0102] In some embodiments, in addition to a combination of some or part of the embodiments or examples described in the present disclosure, one or more UE capability constraint dimensions include constraints on each other.

[0103] In some embodiments, in addition to a combination of some or part of the embodiments or examples described in the present disclosure, the UE further includes a plurality of multi - subscriber identity modules (MUSIMs) corresponding to a first subscription to the first network and a second subscription to the second network.

[0104] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the UE temporary capability constraint further includes constraint information at a granularity level; and / or the granularity level includes at least one of the following: per-UE level, per-band level, per-band combination (BC) level, per-band per-BC level, per-feature set entry per-band level, or per-carrier component per-BC level.

[0105] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the UE temporary capability constraint further includes a first dimension and a second dimension, where: the first dimension includes an affected BC report corresponding to a list of affected BCs, and the second dimension includes a set of parameter restrictions at a granularity level, and the set of parameter restrictions includes at least one of the following: maximum multiple-input multiple-output (MIMO) layer, maximum modulation order, or maximum supported bandwidth.

[0106] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the affected BC report further includes a list of feature set entries corresponding to at least one BC or the dimension of at least one BC in the list of affected BCs, and the list of feature set entries includes at least one of the following: allowed feature set entries, affected feature set entries, or prohibited feature set entries.

[0107] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the first network further receives from the UE at least one of the following: an indication of at least one selected band entry of a second network, and / or an indication of at least one allowed band entry of the first network.

[0108] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the first network further includes a master node and a secondary node; and / or the master node sends capability coordination information to the secondary node, and the capability coordination information includes a list of selected band entries, where the list of selected band entries includes a list of band entries selected by the master node and by the second network.

[0109] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the capability coordination information further includes a set of parameter restrictions corresponding to a list of affected band combinations, and / or the parameter restrictions include at least one of the following: maximum multiple-input multiple-output (MIMO) layer, maximum modulation order, or maximum supported bandwidth.

[0110] In some embodiments, in addition to a part or combination of the embodiments or examples described in the present disclosure, the capability coordination information further includes a set of parameter limitations at a granularity level; and / or the granularity level includes at least one of the following: per-UE level, per-band level, per-band combination (BC) level, per-band per-BC level, per-feature set entry per-band level, or per-carrier component per-BC level.

[0111] The present disclosure describes various exemplary embodiments for user equipment (UE) capability coordination in dual connectivity (DC), which are used as examples and do not impose any limitations on the present disclosure.

[0112] Example Set I

[0113] The present disclosure describes various embodiments, in which, for each BC, various methods may indicate allowed feature set entries, including but not limited to the case of only supporting fallback capabilities.

[0114] Various embodiments can address the problems described below. On the first network (Network A) side, during the registration procedure, the network will request the UE to report UE capabilities. During this procedure, the network may include a frequency list in the UE capability request message, and then, the UE may report the supported band combinations according to this frequency list. Depending on whether the band of the second network (Network B) is included in this list, there may be two cases / situations: Case 1, the band of Network B (e.g., Band Z) is included in the required frequency list of Network A; and Case 2, the band of Network B (e.g., Band Z) is not included in the required frequency list of Network A. These two cases can be represented as follows.

[0115] Case 1: Band Z is required at Network A

[0116] Network A: BandListFilter: Bands X / Y / Z / O / P

[0117] The UE reports the relevant BCs, where the band combinations with Band Z are BC 1 to 4, as follows:

[0118] BC1: X + Y + Z

[0119] BC2: X + O + Z

[0120] BC3: P + Y + Z

[0121] BC4: O + P + Z

[0122] Case 2: Band Z is not required at Network A

[0123] Network A: BandListFilter: Bands X / Y / O / P

[0124] The BCs related to UE reports are as follows:

[0125] BC1: X + Y

[0126] BC2: X + O

[0127] BC3: P + Y

[0128] BC4: O + P

[0129] For case 1, the BCs with frequency band Z and the corresponding feature set combinations can be reported in the UE capability information. Taking BC1 as an example, BC1 includes X + Y + Z, and the UE reports the featuresetCombination of BC1, as shown in Figure 7 Then, for BC1, when the UE has some temporary capability constraints at network A (e.g., due to the actions of network B), the UE can indicate BC1 together with the feature set entries (e.g., the allowed feature set entry 1 / 3, or the prohibited feature set entry 2).

[0130] For case 2, when the frequency band Z is not included in the required frequency list, the UE may not report the BCs with frequency band Z. In some embodiments, there may be the following sub - cases.

[0131] Sub - case 1: The UE can support the original feature set entries in the FeaturesetCombination of the BCs without frequency band Z. For a non - limiting example, refer to Figure 8A , when the UE reports BC1 with a featureSetCombination (including both FeatureSetEntry 1a / 2a) to network A, and when the UE uses frequency band Z to connect to network B, the UE can support the feature set entry 1a at frequency bands X + Y, and then the UE can indicate BC1 with the feature set entry 1a to network A as a temporary capability constraint.

[0132] Sub - case 2: The UE can only support the fallback feature set. In some embodiments, this sub - case may occur when the frequency band of network B is not included in the network required frequency list. For a non - limiting example, refer to Figure 8BWhen the UE reports BC1 with a featureSetCombination (including both FeatureSetEntry1a / 2a) to Network A, and when the UE connects to Network B using Band Z, the UE may only support a lower capability (or fallback capability) than the originally reported featuresetCombination entries. For example, for FeatureSetEntry 1a, it may support a bandwidth of 100 MHz at Band X with 4 MIMO layers; however, when the UE is operating in Band Z simultaneously, the UE may only support a bandwidth of 50 MHz with 2 MIMO layers. Various embodiments can be used to indicate the temporary capability constraints supported for Band X+Y.

[0133] In various embodiments, the UE may indicate some other key limitations for these affected BC lists or for each BC or part of a BC included in the affected BC list (e.g., maximum MIMO layer, maximum modulation order, supported bandwidth, etc.). The temporary capability constraints may include some or all of the following: allowed, affected, and / or prohibited BC information; a list of allowed, affected, and / or prohibited featureset combination entries; and / or dedicated capability parameter constraints (e.g., maximum MIMO layer, maximum modulation order, supported bandwidth, etc.). The dedicated capability parameter limitations can be set at various granularity levels, such as but not limited to, for all BCs, for each BC, for a part of a BC, for each featureset combination entry of each BC, for the UE, for the frequency band. These dedicated parameters can also be reported separately for UL and DL at the above-mentioned granularity.

[0134] In some embodiments, the UE may perform BC reporting together with some capability constraints. In other words, these dedicated capability parameters can be used to indicate the fallback capability, and one or more of the following parameters can be reported at various granularity levels.

[0135] For a non-limiting example, refer to Figure 9 the dedicated capability reporting levels include at least one of per BC (910), per frequency band per BC (920), per featuresetEntry per frequency band (930), or per carrier component (cc) per BC (940).

[0136] In some embodiments, the dedicated capability may be reported at the per UE level, so that all BCs should comply with these UE-level constraints.

[0137] In some embodiments, the dedicated capability may be reported at the per frequency band level, so that all relevant frequency bands in each BC should comply with these frequency band-level constraints.

[0138] Some non - limiting examples of per - UE level reporting are described below. For per - UE level reporting, the temporary capability constraints can include 2 parts (or two dimensions), where each part / dimension can impose constraints on the other part / dimension. The first part / dimension (part 1 or dimension 1) can include the list of affected BCs (including the list of allowed and / or prohibited BCs) and / or one or more related FeatureSetEntries. The second part / dimension (part 2 or dimension 2) can include per - UE specific parameters (e.g., maximum MIMO layers, maximum modulation order, supported bandwidth, etc.). The supported MIMO layers / modulation order / bandwidth can be determined by the lower capability between part 1 and part 2. For example, for MIMO layers, when part 1 includes 4 MIMO layers and part 2 includes a maximum of 2 MIMO layers, the supported MIMO layer is determined to be 2 because 2 MIMO layers is the lower capability between 4 MIMO layers and 2 MIMO layers.

[0139] For an example of per - UE level reporting, refer to Figure 10A , part 1 includes the affected BC report, and part 2 includes a maximum number of MIMO layers = 2 and a maximum bandwidth per band = 80 MHz. In some embodiments, the maximum bandwidth can be reported as 80 MHz per CC. In the figures of the present disclosure, "M" of the bandwidth refers to "MHz".

[0140] Figure 10B The final supported capabilities determined by the lower capability between part 1 and part 2 are shown.

[0141] Some non - limiting examples of per - band level reporting are described below. For per - band level reporting, the temporary capability constraints will include 2 parts (or two dimensions), where each part / dimension can impose constraints on the other part / dimension. The first part / dimension (part 1 or dimension 1) can include the list of affected BCs (including allowed or prohibited BCs), which can also include one or more related FeatureSetEntries. The second part / dimension (part 2 or dimension 2) can include per - band specific parameters (e.g., maximum MIMO layers, maximum modulation order, supported bandwidth, etc.). The supported MIMO layers / modulation order / bandwidth can be determined by the lower capability between part 1 and part 2.

[0142] For an example of per - band level reporting, refer to Figure 11A , part 1 includes the affected BC report, and part 2 includes: for band X, a maximum number of MIMO layers = 4 and a bandwidth per band (or per CC) = 80 MHz; for band Y, a maximum number of MIMO layers = 2; and for band O, there are no constraints.

[0143] Figure 11B Shows the final supported capabilities determined by the lower capabilities between Part 1 and Part 2.

[0144] Some non-limiting examples of per BC level reports are described below. For each BC level report, the temporary capability constraints can include 2 parts (or two dimensions), where each part / dimension can impose constraints on the other part / dimension. The first part / dimension (Part 1 or Dimension 1) can include the list of affected BCs (including allowed or prohibited BCs), and can also include one or more related FeatureSetEntries, which can be reported by index according to the reported UE capability information. For example, the index 1 corresponding to the first BC reported in the list of supported BCs in the UE capabilities.

[0145] For each affected BC (or part of a BC), the second part / dimension (Part 2 or Dimension 2) can include dedicated parameters (e.g., maximum MIMO layers, maximum modulation order, supported bandwidth, etc.). The supported MIMO layers / modulation order / bandwidth can be determined by the lower capabilities between Part 1 and Part 2.

[0146] For examples of per BC level reports, refer to Figure 12A , Part 1 includes the affected BC reports, and Part 2 includes some dedicated parameters.

[0147] Figure 12B Shows the final supported capabilities determined by the lower capabilities between Part 1 and Part 2.

[0148] Some non-limiting examples of per band per BC level reports are described below. For each BC level report, the temporary capability constraints can include 2 parts (or two dimensions), where each part / dimension can impose constraints on the other part / dimension. The first part / dimension (Part 1 or Dimension 1) can include the list of affected BCs (including allowed and / or prohibited BCs), and can also include one or more related FeatureSetEntries, which can be reported by index according to the reported UE capability information. For example, the index 1 corresponding to the first BC reported in the list of supported BCs in the UE capabilities. For each band of each affected BC (or part of a BC), the second part / dimension (Part 2 or Dimension 2) can include dedicated parameters (e.g., maximum MIMO layers, maximum modulation order, supported bandwidth, etc.). The supported MIMO layers / modulation order / bandwidth can be determined by the lower capabilities between Part 1 and Part 2.

[0149] For examples of per band per BC level reports, refer to Figure 13A , Part 1 includes the affected BC reports, and Part 2 includes some dedicated parameters.

[0150] Figure 13B Shows the final support ability determined by the lower ability between part 1 and part 2.

[0151] Various embodiments / implementations in the present disclosure can be similarly applied to other levels of ability constraint reports, including but not limited to per FeaturesetEntry per band and / or per cc per BC, where a similar logical flow can be used, and one of the differences is that dedicated parameters are reported with a greater granularity.

[0152] In various embodiments / implementations described in the present disclosure, each BC in the affected BC list can be indicated by an index that indicates the position of the band combination in the list of supported band combinations included in the UE ability report. As an enhancement, when the network configures the UE to report MUSIM assistance information, it can also include one or more band information (e.g., having a band number or an absolute radio frequency channel number (ARFCN) value).

[0153] For a non-limiting example, in the MUSIM assistance information report configuration, Reconfiguration->OtherConfig->MusimConfig->Bandlist can include Bandlist[0]=Nx, Bandlist[2]=Ny, and / or Bandlist[2]=Nz, where Nx, Ny, and / or Nz are non-negative integers.

[0154] In some implementations, in addition to using the band number or ARFCN value, it can also be indicated by an index that indicates the position of the band in the band list of the UE ability requirement message. When the UE reports the affected BC, the UE can only indicate the BC that includes the bands configured by the network (e.g., when the network configures the UE to report MUSIM assistance information).

[0155] For a non-limiting example, referring to Figure 14 , a method can include some or all of the following steps.

[0156] Step 1410: The network (1490) configures the UE (1480) to report UE ability using a band list (e.g., including band x, band y, band z, band o, and band p).

[0157] Step 1420: The UE reports UE ability with the list of supported BCs, and the supported band combinations are BCs composed of one or more of the bands (x, y, z, o, and / or p).

[0158] Step 1430: The network configures the UE to report MUSIM assistance information, which may include a list of frequency bands for MUSIM reporting (e.g., band x, band y, band z, band o, and / or band p).

[0159] Step 1440: The UE may report a list of BCs affected by MUSIM, which includes only the BCs of the frequency bands in the frequency band list of Step 1430. The list of affected BCs may be indicated by one or more indices, and each index indicates the position of a frequency band combination in the list of supported frequency band combinations included in the UE capability report in Step 1420.

[0160] This disclosure describes various exemplary embodiments of UE capability coordination in the dual-active state, which are used as examples and do not impose any limitations on this disclosure.

[0161] Example Set II

[0162] This disclosure describes various embodiments, in which, for each BC, various methods may indicate one or more selected frequency band entries, such as but not limited to, indicating one or more frequency band entries of network B, or indicating one or more allowed frequency band entries of network A.

[0163] Various embodiments can solve the problems described below. For the above cases: Case 1: The frequency band of network B (e.g., band Z) is included in the required frequency list of network A; and Case 2: Band Z is not included in the required frequency list of network A. These two cases can be represented as follows.

[0164] Case 1: Band Z is required at network A

[0165] Network A: BandListFilter: Bands X / Y / Z / O / P

[0166] The UE reports the relevant BCs, where the frequency band combinations with band Z are BC 1 to 4, as follows:

[0167] BC1: X + Y + Z

[0168] BC2: X + O + Z

[0169] BC3: P + Y + Z

[0170] BC4: O + P + Z

[0171] Case 2: Band Z is not required at network A

[0172] Network A: BandListFilter: Bands X / Y / O / P

[0173] The UE reports the relevant BCs as follows:

[0174] BC1: X + Y

[0175] BC2: X + O

[0176] BC3: P + Y

[0177] BC4: O + P

[0178] In some embodiments, in addition to the list of affected bands, Network A also needs to know which bands are allowed on the Network A side. For the above Case 2, only Network A bands are included, but for Case 1, the bands of both networks are included in each BC.

[0179] Various embodiments provide methods for determining which bands are allowed at Network A, and the method may include at least one of the following two options. For Option A, the UE indicates the selected band entries of Network B; and for Option B, the UE indicates the band entries allowed by Network A.

[0180] For a non-limiting example, the UE works with Network B in Band Z and with Network A in Band X + Y.

[0181] For Option A, for Case 1, the UE indicates Band Z as the selected band entry; or for Case 2, the UE may not indicate any bands because no BC includes the band entry Z.

[0182] For Option B, for Case 1, the UE may indicate Band X + Y (or other band entries that can work with Band Z). For example, the allowed band entries may include BC1: X + Y, BC2: X + O, BC3: P + Y, and / or BC4: O + P. For Case 2, the allowed band entries may include BC1: X + Y, BC2: X + O, BC3: P + Y, and / or BC4: O + P, where in some embodiments, there is also a case where a part of the BC is reported as a fallback for other BCs. For example, instead of reporting BC1, the UE reports BC5: X + Y + O, and then the UE may indicate BC5 with the allowed band entries X and Y.

[0183] Example Set III

[0184] This disclosure describes various embodiments that can solve the problems described below. Refer to Figure 15A, adopting a multi-radio access technology (Multi-RAT) (MR) dual connectivity (DC) (MR-DC) architecture, the master node (MN) can indicate the selected band entries on the MN side to the secondary node (SN), and then the SN can further select the band on the SN side. As described in this disclosure, when the UE reports BCs including both the network A and network B sides, and when network A operates under the MR-DC architecture, there are problems / difficulties associated with how the MN indicates band entry information to the SN and / or how the MN indicates the constraints related to the feature set to the SN. See Figure 15B , Step 1: The UE indicates temporary capability constraints (e.g., the affected BC list, the affected feature set entries for each BC, dedicated capability parameters, etc.); Step 2: The MN determines the allowed BC list and the selectedBandEntriesMNList; Step 3: The SN responds to the MN; and / or Step 4: The MN sends a reconfiguration to the UE.

[0185] Various embodiments describe methods for band entry indication, which can solve the problems / difficulties of how to set the selected band entries by the MN and / or how to indicate the temporary capability constraints to the SN in Figure 15B Step 2. In these methods, the selected band entries of both the MN and other networks (e.g., network B) can be included in the SelectedBandEntriesMN, as shown below (MN->SN).

[0186] BandCombinationInfoList::=SEQUENCE(SIZE(1..maxBandComb)) OF BandCombinationInfo

[0187] BandCombinationInfo::=SEQUENCE{

[0188] bandCombinationIndex BandCombinationIndex,

[0189] allowedFeatureSetsList SEQUENCE(SIZE

[0190] (1..maxFeatureSetsPerBand)) OF FeatureSetEntryIndex

[0191] }

[0192] selectedBandEntriesMNList SEQUENCE(SIZE(1..maxBandComb)) OF SelectedBandEntriesMN

[0193] SelectedBandEntriesMN ::= SEQUENCE(SIZE

[0194] (1..maxSimultaneousBands)) OF BandEntryIndex

[0195] In the above content, for SelectedBandEntriesMN, selected band entries for both MN and other networks (such as the bands of Network B) should be included.

[0196] For a non-limiting example, one case can be represented as follows.

[0197] Case 1: Band Z is required at Network A

[0198] Network A: BandListFilter: Bands X / Y / Z / O / P

[0199] The UE reports relevant BCs, where the band combinations with Band Z are BC 1 to 4, as follows:

[0200] BC1: X + Y + Z

[0201] BC2: X + O + Z

[0202] BC3: P + Y + Z

[0203] BC4: O + P + Z

[0204] For Case 1, taking BC1 as an example, when Network A selects Band X at the master cell group (MCG), and then the MCG can include Band X and Band Z as selected band entries at the MN side. In addition, the MCG can only select the featuresetEntry allowed in the MUSIM UAI.

[0205] Various embodiments describe methods for feature set entry constraint indication. For MN->SN, MN needs to indicate dedicated parameter restrictions to SN. The dedicated capability constraints can also be forwarded to SCG. Taking the dedicated capability constraint report at each BC level as an example, the UE reports the allowed BC1 / BC2 to MN, with dedicated capability constraints at each BC level. In Figure 15B step 2, MN can also forward these dedicated capability constraints to SN, for example, the constraint information as Figure 12A shown.

[0206] In all of the above solutions, the dedicated parameters may also be reported separately for UL / DL (or only for UL or only for DL) at the above granularity. The parameters of the second dimension (e.g., dedicated parameters) may be any of the parameters included in the first dimension (e.g., affected band combinations).

[0207] Example Set IV

[0208] This disclosure describes various embodiments for solving problems related to scheduling gaps. For a MUSIM UE, the UE may request multiple per-UE scheduling gaps (e.g., 3 periodic gaps and 1 aperiodic gap). The network may configure the per-UE gaps according to the UE's request. When the UE operates in an MR-DC configuration in Network A, the MN needs to coordinate with the SN regarding the per-UE gaps, where the per-UE gaps mean that they can be applied on both the MN and SN sides. Referring to Figure 16 , the general procedure may include some or all of the following steps.

[0209] Step 1610, the UE sends a UAI to the MN, and the UAI may include gap configurations as follows. MUSIM-Assistance-r17::= SEQUENCE{

[0210] musim-PreferredRRC-State-r17 ENUMERATED{idle,inactive,outOfConnected} OPTIONAL,

[0211] musim-GapPreferenceList-r17 MUSIM-GapPreferenceList-r17 OPTIONAL}

[0212] MUSIM-GapPreferenceList-r17::= SEQUENCE(SIZE(1..4)) OF MUSIM-GapInfo-r17

[0213] Step 1620, the MN determines the accepted gap requests and sends them to the SN.

[0214] In the CG-ConfigInfo, there are two options. The first option may include reusing the MUSIM-GapConfig-r17 structure, which may support incremental configuration as follows.

[0215] MUSIM-GapConfig-r17::= SEQUENCE{

[0216] musim-GapToReleaseList-r17 SEQUENCE(SIZE(1..3))OF MUSIM-GapId-r17OPTIONAL,--Need N

[0217] musim-GapToAddModList-r17 SEQUENCE(SIZE(1..3))OF MUSIM-Gap-r17OPTIONAL,--Need N

[0218] musim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL,--Need N ...

[0220] }

[0221] MUSIM-Gap-r17::=SEQUENCE{

[0222] musim-GapId-r17 MUSIM-GapId-r17,

[0223] musim-GapInfo-r17 MUSIM-GapInfo-r17

[0224] }

[0225] The second option does not include incremental configuration as follows.

[0226] MUSIM-GapConfigINM-r17::=SEQUENCE{

[0227] musim-PerioidcGaoList-r17 SEQUENCE(SIZE(1..3))OF MUSIM-Gap-r17OPTIONAL,--Need N

[0228] musim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL,--Need N}

[0229] Step 1630, the SN determines the accepted gap request and sends it to the MN in CG-Configure as follows.

[0230] MUSIM-GapConfigSCG-r17::=SEQUENCE{

[0231] musim-GapList-r17 SEQUENCE(SIZE(1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need N

[0232] musim-AperiodicGap-r17 Enum(Accepted) OPTIONAL, -- Need N}

[0233] Step 1640, for MUSIM GAP configuration, the MN sends the configuration to the UE as follows. MUSIM-GapConfig-r17 ::= SEQUENCE {

[0234] musim-GapToReleaseList-r17 SEQUENCE(SIZE(1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need N

[0235] musim-GapToAddModList-r17 SEQUENCE(SIZE(1..3)) OF MUSIM-Gap-r17 OPTIONAL, -- Need N

[0236] musim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL, -- Need N ...

[0238] }

[0239] MUSIM-Gap-r17 ::= SEQUENCE {

[0240] musim-GapId-r17 MUSIM-GapId-r17,

[0241] musim-GapInfo-r17 MUSIM-GapInfo-r17

[0242] }

[0243] MUSIM-GapInfo-r17 ::= SEQUENCE {

[0244] musim-Starting-SFN-AndSubframe-r17 MUSIM-Starting-SFN-AndSubframe-r17 OPTIONAL, -- Cond aperiodic

[0245] musim-GapLength-r17 ENUMERATED{ms3,ms4,ms6,ms10,ms20}

[0246] OPTIONAL,--Cond gapSetup

[0247] musim-GapRepetitionAndOffset-r17 CHOICE{

[0248] ms20-r17 INTEGER(0..19),

[0249] ms40-r17 INTEGER(0..39),

[0250] ms80-r17 INTEGER(0..79),

[0251] ms160-r17 INTEGER(0..159),

[0252] ms320-r17 INTEGER(0..319),

[0253] ms640-r17 INTEGER(0..639),

[0254] ms1280-r17 INTEGER(0..1279),

[0255] ms2560-r17 INTEGER(0..2559),

[0256] ms5120-r17 INTEGER(0..5119), ...

[0258] }OPTIONAL--Cond periodic

[0259] }

[0260] MUSIM-Starting-SFN-AndSubframe-r17::=SEQUENCE{

[0261] starting-SFN-r17 INTEGER(0..1023),

[0262] startingSubframe-r17 INTEGER(0..9)

[0263] }

[0264] Example Set V

[0265] In some embodiments, for network energy saving in NR, the goal regarding SSB-less cells is to specify SSB-less SCell operation for FR1 and inter-band CA of co-located cells, where feasible according to some research findings. In this case, the UE measures the SSB transmitted on the PCell or another SCell to achieve time / frequency synchronization of the SCell (including downlink AGC), as well as L1 / L3 measurements, including potential enhancements to the SCell activation procedure if necessary.

[0266] In some embodiments, SSB-less SCells for intra-band CA can be supported. The timing and frequency synchronization of SSB-less SCells can depend on the co-located SpCell. For TA maintenance, the SSB-less SCell and the co-located SpCell are in the same TAG, which can be ensured by NW embodiments. For the UL and DL relationship, the path loss reference for power control of SRS, PUCCH, and PUSCH in the SCell can be derived from CSI-RS or SSB in the SpCell via RRC configuration, and the spatial relationship of PUCCH and SRS in the SCell can be derived from CSI-RS or SSB in the SpCell via RRC configuration. For cross-carrier scheduling, the PUSCH in the SCell can be scheduled by the PDCCH in the SpCell. For RRM, in the co-located scenario, the addition / change / release of SSB-less SCells can be performed based on the measurement results of the co-located SpCell, and this can be left to NW implementation. Therefore, no measurement objects for SSB-less SCells can be configured. The UE can obtain the timing and frequency synchronization of the SSB-less SCell from the SpCell.

[0267] Regarding the definitions of SSB_less SCell types and SSB_less BC types, for SSB-less SCells of inter-band CA, one difference between SSB-less SCells of inter-band CA and SSB-less SCells of intra-band CA lies in UE capability reporting. For example, new UE capabilities are introduced to indicate support for inter-band Scells without SSB.

[0268] SSB_less secondary cells include the following types: Type 1: SSB_less secondary cells with DL PDSCH / TRS / CSI-RS in DL resources; Type 2: SSB_less secondary cells without TRS / CSI-RS but with PDSCH (PDSCH is configured, but TRS / CSI-RS is not configured); and Type 3: SSB_less secondary cells without any DL resources (i.e., no DL resources are configured in RRC).

[0269] From the perspective of UE capabilities, this means that the UE can implicitly or explicitly indicate a band combination with an SSB_less band entry (abbreviated as SSB_less BC), and also includes 3 types of SSB_less band entries, which at least include: Type 1: One or more SSB_less band entries that support DL resources with DL PDSCH / TRS / CSI-RS; Type 2: One or more SSB_less band entries without TRS / CSI-RS but with PDSCH; and / or Type 3: One or more SSB_less band entries that do not support any DL resources.

[0270] Regarding implicit reporting (per band pair), the implicit mode means that the UE does not immediately indicate the BC with an SSB_less band entry, but the UE indicates per band pair level information, and then the SSB_less BC can be further determined through the normal band combination and this per band pair level information. For example, the UE indicates a potential "reference band list" for each band that supports SSB_less secondary cells, which means that the "reference band list for each inter-band SSB_less secondary cell supporting band" is independently configured (independent of the band combination), and it applies to all band combinations.

[0271] On the network side, an inter-band SSB_less secondary cell can only be configured when a serving cell with an SSB on the corresponding potential "reference" band is configured in the CA operation.

[0272] Figure 17A An example of the reference band list report per band pair is shown.

[0273] The UE can indicate a reference band list in parallel with the supported band combinations, in which it indicates the feasible reference band list for each band that supports SSB_less secondary cells.

[0274] Figure 17B An example of the reference band list structure is shown.

[0275] For a non-limiting example, the UE reports 2BCs as BC1: Band A + Band B + Band C, and BC2: Band A + Band B + Band D. In addition, the UE also reports a reference band list for Band B (Band C, Band D), which means the UE can support the following SSB_Less BCs (referred to as BC1a / BC2a), where BC1a: Band A + Band B + Band C (SSB_less), and BC2a: Band A + Band B + Band D (SSB_less).

[0276] At the network side, when configuring Band B in CA operation, the network can configure an SSB-less SCell on Band C or Band D.

[0277] In some embodiments, for the reference band list, the following alternatives can be considered.

[0278] (1) For each band that supports an SSB-less inter-band SCell, report a band list to indicate the bands that can be used as reference bands for the SSB-less inter-band SCell. The inter-band SSB-less SCell can be configured only when at least one serving cell on the reference band is configured in CA operation.

[0279] (2) For each band that can be used as a reference band for the inter-band SSB-less SCell, report a band list that supports the SSB-less SCell to indicate the applicable bands for the SSB-less inter-band SCell. When a serving cell with SSB is configured on the reference band, the inter-band SSB-less SCell on the applicable band list can be configured.

[0280] (3) Configure one or more band lists or band groups. The bands within the same list / group can be used as reference bands for each other. When a serving cell with SSB is configured in CA operation, the inter-band SSB-less SCell can be configured on another band within the same list / group.

[0281] In some embodiments, in addition to the band information, the SSB-less SCell type can also be included in the band list / band group to indicate the type of supported SSB-less SCell.

[0282] Regarding the explicit reporting method (per band combination), the explicit method means that the UE can explicitly indicate the supported SSB_Less BCs, for example, at the granularity of each BC. The "reference band list for each band that supports an SSB-less inter-band SCell" will be reported per BC. Generally, there are 5 solutions for the explicit method.

[0283] Solution 1 includes adding a new BC list for SSB_Less BC. Figure 17C An example of the new BC list for SSB_Less BC is shown. With this solution, the UE can indicate the supported SSB_less BCs in a separate list, and in each SSB_less BC, the UE also indicates a reference band list to indicate which band can be used as a reference band. On the network side, an inter-band SSB-less SCell can be configured only if a serving cell with an SSB on the corresponding potential "reference" band is configured in CA operation. In addition, the UE can also indicate the featruesetCombination ID and / or other parameters different from the basic BC.

[0284] Solution 2 includes adding one or more new band entries to the basic BC.

[0285] One or more new band entries can be used to indicate the bands supporting SSB_Less Scell. For the new band entries, the UE can also indicate a reference band list to indicate which band can be used as a reference band. On the network side, an inter-band SSB-less SCell can be configured only when a serving cell with an SSB on the corresponding potential "reference" band is configured in CA operation. In addition, the UE can also indicate the featruesetCombination ID and / or other parameters different from the basic BC.

[0286] Figure 17D An example of the new SSB_less band entry of the basic BC is shown.

[0287] As a non-limiting example, the UE supports the basic BC1 including A + B and the SSB_less BC BC2 including A + B + C (SSB_less band entry), and the reference band for band C is band B. The UE can include BC1 including A + B in the above band combination, then add band C in the newly added BandParametersSSBLess, and set band B as the reference band for band C. The UE can additionally report the featureSetCombinationID in the newly added "featureSetCombinationIDSSBLess" field, or one or more feature sets of the SSB_less band C.

[0288] Solution 3 includes a legacy BC structure with featuresetDownlink ID = 0 to indicate the case of SSB_Less without DL resources (or only UL) (e.g., type 3). In some embodiments, this solution can be applied to type 3, where type 3 includes one or more SSB-less band entries that do not support any DL resources.

[0289] In some embodiments, setting the downlink feature set of an SSB_Less band entry to 0 may indicate no DL resources on this band entry.

[0290] Figure 17E An example of an SSB_Less band entry without DL is shown.

[0291] For example, referring to Figure 4 , if the UE reports BC band 1 + band 2 + band 3 with feature set entry 1 / 2, and reports SSB_less BC band 1 + Band 2 + band 3 (SSB_less) with feature set entry 3, where band 3 is an SSB_less band without DL resources, then the UE can set the FeatureSetDownlinkId of FeatureSet3.3 to 0.

[0292] In some embodiments, for a legacy gNB that may not support the SSB_Less function, it may only consider featureSetEntry 1 / 2 and ignore featureSetEntry 3, while the new gNB (supporting the SSB_less feature) can read FeatureSetEntry 3 and use it for SSB_Less BC band 1 + band 2 + band 3 (SSB_Less).

[0293] Solution 4 includes indicating the SSB_Less type in the feature set. In some embodiments, referring to Figure 17F , the UE can indicate the supported SSB_Less type (at least the 3 types defined above) in the FeatureSet or FetrueSetDownlink.

[0294] Solution 5 includes indicating the SSB_Less type in the BC. In this solution, the SSB_Less type of the band supporting SSB_less is indicated at the BC level.

[0295] In the SSB_Less support indication, referring to Figure 17G and / or Figure 17H , it can indicate the SSB_Less type of each band supporting SSB_Less and / or the reference band list.

[0296] In some embodiments, for the above solutions 3 / 4 / 5, the "reference band list for each inter-band supporting SSB-less SCell bands" may be reported per BC.

[0297] In some embodiments, for the reference band list structure with the above explicit solutions, the following alternatives may be considered.

[0298] (1) For each band that supports SSB-less inter-band SCell thereon, report a band list to indicate the bands that can be used as reference bands for SSB-less inter-band SCell. The inter-band SSB-less SCell can be configured only if at least one serving cell on the reference band is configured in the CA operation.

[0299] (2) For each band that can be used as a reference band for inter-band SSB-less SCell, report a band list of bands supporting SSB-less SCell to indicate the applicable bands for inter-band SSB-less SCell. When a serving cell with SSB is configured on the reference band, the inter-band SSB-less SCell on the applicable band list can be configured.

[0300] (3) Configure one or more band lists or band groups. The bands within the same list / group can be used as reference bands for each other. If a serving cell with SSB is configured in the CA operation, the inter-band SSB-less SCell can be configured on another band within the same list / group.

[0301] In addition, in addition to the band information, the SSB-less SCell type may also be included in the band list / band group to indicate the type of supported SSB-less SCell.

[0302] In some embodiments, the method may include any combination of the above solutions. The above UE capability structure is not limited to indicating the SSB_less feature, and it can also be extended to any other feature having certain special characteristics on one or more bands of the band combination.

[0303] The present disclosure describes methods, apparatuses, and computer-readable media for wireless communication. The present disclosure solves the problem / difficulty of user equipment (UE) capability coordination in dual connectivity (DC). The methods, devices, and computer-readable media described in the present disclosure can promote the performance of wireless transmission between the user equipment and multiple network nodes, thereby improving efficiency and overall performance. The methods, devices, and computer-readable media described in the present disclosure can improve the overall efficiency of the wireless communication system.

[0304] References in this specification to features, advantages, or similar language do not imply that all features and advantages that can be implemented by the solution should or are included in any single embodiment thereof. On the contrary, language referring to features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, discussions of features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.

[0305] In addition, in one or more embodiments, the features, advantages, and characteristics of the solution may be combined in any suitable manner. Based on the description herein, those of ordinary skill in the relevant art will recognize that the solution may be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be identified that may not be present in all embodiments of the solution.

Claims

1. A method for wireless communication, the method comprising: Sending, by a user equipment (UE), UE assistance information including UE temporary capability constraints to a first network, the UE capability constraints indicating to the first network one or more constraint dimensions.

2. The method according to claim 1, wherein: One or more UE capability constraint dimensions include constraints on each other.

3. The method according to claim 1, wherein: The UE includes a plurality of multi - universal subscriber identity modules (MUSIMs) corresponding to a first subscription of the first network and a second subscription of a second network.

4. The method according to any one of claims 1 to 3, wherein: The UE temporary capability constraints include constraint information at a granularity level; and The granularity level includes at least one of the following: per - UE level, per - band level, per - band combination (BC) level, per - band per - BC level, per - feature - set - entry per - band level, or per - carrier - component per - BC level.

5. The method according to claim 4, wherein: The UE temporary capability constraints include a first dimension and a second dimension, wherein: The first dimension includes an affected BC report corresponding to a list of affected BCs, The second dimension includes a set of parameter limitations at the granularity level, The set of parameter limitations includes at least one of the following: maximum multiple - input multiple - output (MIMO) layer, maximum modulation order, or maximum supported bandwidth.

6. The method according to claim 5, wherein: The affected BC report further includes a list of feature - set entries corresponding to at least one BC or a part of the at least one BC in the list of affected BCs, and The list of feature - set entries includes at least one of the following: allowed feature - set entries, affected feature - set entries, or prohibited feature - set entries.

7. The method according to any one of claims 1 to 3, wherein: The UE temporary capability constraints include a first dimension and a second dimension, wherein: The first dimension includes an affected BC report corresponding to a list of affected BCs of the UE, and The second dimension includes a set of parameter limitations of the UE; and The UE determines the set of supported parameters by: For each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter limitations of the UE.

8. The method according to any one of claims 1 to 3, wherein: The UE temporary capability constraints include a first dimension and a second dimension, wherein: The first dimension includes an affected BC report corresponding to a list of affected BCs having a list of feature - set entries, and The second dimension includes a set of parameter limitations for each band; and The UE determines the set of supported parameters by: For each parameter in the supported parameters, using the lower UE capability between the affected BC report and the set of parameter limitations of the band.

9. The method according to any one of claims 1 to 3, wherein: The UE temporary capability constraints include a first dimension and a second dimension, wherein: The first dimension includes an affected BC report corresponding to a list of affected BCs with a list of feature set entries, and the second dimension includes a set of parameter restrictions for each BC in the list of affected BCs or for a part of each BC; and the UE determines the set of supported parameters by for each parameter among the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions for each BC or for a part of each BC.

10. The method according to any one of claims 1 to 3, wherein: the UE temporary capability constraint includes a first dimension and a second dimension, wherein: the first dimension includes an affected BC report corresponding to a list of affected BCs with a list of feature set entries, and the second dimension includes a set of parameter restrictions for each frequency band of each BC in the list of affected BCs or for a part of each BC; and the UE determines the set of supported parameters by for each parameter among the supported parameters, using the lower UE capability between the affected BC report and the set of parameter restrictions for each frequency band of each BC or for a part of each BC.

11. The method according to any one of claims 4 to 10, wherein: the list of affected BCs includes at least one of the following at least: allowed BCs or prohibited BCs; and each frequency band in the list of affected BCs is represented by at least one of the following: a frequency band number, an absolute radio frequency channel number (ARFCN) value, or an index, where the index indicates the position of the frequency band in the list of frequency bands in the UE capability request message.

12. The method according to any one of claims 1 to 3, wherein: the UE indicates at least one of the following to the first network: at least one selected frequency band entry indicating a second network, or at least one allowed frequency band entry indicating the first network.

13. A method for wireless communication, the method comprising: receiving, by a first network, from a user equipment (UE) UE assistance information including a UE temporary capability constraint, the UE capability constraint indicating to the first network one or more constraint dimensions.

14. The method according to claim 13, wherein: the UE temporary capability constraint includes constraint information at a granularity level; and the granularity level includes at least one of the following: per-UE level, per-frequency band level, per-band combination (BC) level, per-frequency band per-BC level, per-feature set entry per-frequency band level, or per-carrier component per-BC level.

15. The method according to claim 14, wherein: the UE temporary capability constraint includes a first dimension and a second dimension, wherein: the first dimension includes an affected BC report corresponding to a list of affected BCs, the second dimension includes a set of parameter restrictions at the granularity level, and the set of parameter restrictions includes at least one of the following: maximum multiple input multiple output (MIMO) layers, maximum modulation order, or maximum supported bandwidth.

16. The method according to claim 14, wherein: The affected BC report also includes a list of feature set entries corresponding to at least one BC in the list of affected BCs or the dimensions of the at least one BC, and the list of feature set entries includes at least one of the following: permitted feature set entries, affected feature set entries, or prohibited feature set entries.

17. The method according to claim 13, wherein: the first network receives from the UE at least one of the following: at least one selected band entry indicating a second network, or at least one permitted band entry indicating the first network.

18. The method according to claim 13, wherein: the first network includes a master node and a secondary node; and the master node sends capability coordination information to the secondary node, the capability coordination information including a list of selected band entries, wherein the list of selected band entries includes a list of band entries selected by the master node and a second network.

19. The method according to claim 18, wherein: the capability coordination information further includes a set of parameter restrictions corresponding to a list of affected band combinations, and the parameter restrictions include at least one of the following: maximum multiple-input multiple-output (MIMO) layer, maximum modulation order, or maximum supported bandwidth.

20. The method according to claim 18, wherein: the capability coordination information further includes a set of parameter restrictions at a granularity level; and the granularity level includes at least one of the following: per-UE level, per-band level, per-band combination (BC) level, per-band per-BC level, per-feature set entry per-band level, or per-carrier component per-BC level.

21. A wireless communication device, which includes a processor and a memory, wherein, The processor is configured to read the code from the memory and implement the method according to any one of claims 1 to 20.

22. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 20.

Images