Frequency resource aggregation

Abstract

Example embodiments of the present disclosure relate to frequency resource aggregation. A method includes sending, to a second apparatus, capability-related information indicating at least one of switching-related capabilities between different frequency domain resources, whether the first apparatus supports switching between different resource aggregation patterns, a maximum number of configured resource aggregation patterns supported by the first apparatus, or a maximum number of frequency domain resources associated with resource aggregation patterns supported by the first apparatus; and receiving, from the second apparatus, configuration information indicating at least one resource aggregation pattern determined by the second apparatus based at least in part on the capability-related information.

Description

Cross-references to related applications

[0001] This application claims priority and benefit to EP application No. 25172153.6, filed on April 24, 2025, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0002] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more particularly to methods, apparatuses, devices, and computer-readable storage media for frequency resource aggregation. Background Technology

[0003] In wireless communication systems, frequency domain resources can be aggregated to improve communication performance. However, frequency resource aggregation may be limited by user equipment (UE) capabilities and radio rules. Therefore, a flexible and efficient resource aggregation solution is desired. Summary of the Invention

[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first apparatus to: send capability-related information to a second apparatus, the capability-related information indicating at least one of the following: handover capability between different frequency domain resources, whether the first apparatus supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first apparatus, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first apparatus; and receive configuration information from the second apparatus indicating at least one resource aggregation pattern, the at least one resource aggregation pattern being determined by the second apparatus at least in part based on the capability-related information.

[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the second apparatus to: receive capability-related information from a first apparatus, the capability-related information indicating at least one of the following: handover capability between different frequency domain resources, whether the first apparatus supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first apparatus, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first apparatus; determine at least one resource aggregation pattern based at least in part on the capability-related information; and send configuration information including the at least one resource aggregation pattern to the first apparatus.

[0006] In a third aspect of this disclosure, a method is provided. The method includes: sending capability-related information to a second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether a first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; and receiving configuration information from the second device indicating at least one resource aggregation pattern, the at least one resource aggregation pattern being determined by the second device at least in part based on the capability-related information.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving capability-related information from a first device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; determining at least one resource aggregation pattern based at least in part on the capability-related information; and sending configuration information including the at least one resource aggregation pattern to the first device.

[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for transmitting capability-related information to a second apparatus, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first apparatus supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first apparatus, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first apparatus; and components for receiving configuration information from the second apparatus indicating at least one resource aggregation pattern, the at least one resource aggregation pattern being determined by the second apparatus at least in part based on the capability-related information.

[0009] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving capability-related information from a first apparatus, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first apparatus supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first apparatus, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first apparatus; components for determining at least one resource aggregation pattern based at least partially on the capability-related information; and components for transmitting configuration information including at least one resource aggregation pattern to the first apparatus.

[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a third aspect.

[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0012] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0013] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2A Example resource aggregation patterns are shown according to some example embodiments of this disclosure; Figure 2B Another example resource aggregation pattern is shown according to some example embodiments of this disclosure; Figure 3 Example signaling flows for communication are shown according to some example embodiments of this disclosure; Figure 4 Example signaling flows for communication are shown according to some example embodiments of this disclosure; Figure 5 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 6 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 9 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 10 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 11 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 12 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0014] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0015] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. In addition to the methods described below, the embodiments described herein can be implemented in various other ways.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0017] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is to be noted that those skilled in the art will recognize, whether explicitly described or not, that such a feature, structure, or characteristic applies in conjunction with other embodiments.

[0018] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0019] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0020] As used herein, unless explicitly stated otherwise, the “responding to A” action does not mean that the action is performed immediately after “A” occurs, but may include one or more intermediate steps.

[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprising,” “having,” “containing,” and / or “including” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0022] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor having software (including digital signal processors, software, and memory, which work together to enable a device such as a mobile phone or server to perform various functions), and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may not exist when the software is not required to operate.

[0023] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0024] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that can implement this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.

[0025] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a repeater, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a Non-Terrestrial Network (NTN) or Non-Terrestrial Network device (such as satellite network device, Low Earth Orbit (LEO) satellite and Geostationary Earth Orbit (GEO) satellite, spacecraft network device, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a UE toward its parent node, while the DU portion of the IAB node behaves similarly to a base station toward the next-hop IAB node.

[0026] As used herein, the term "network device" can also refer to a core network (CN) entity / node / function / device / equipment. An example core network node may include one or more of the following functions: Location Management Function (LMF), Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0027] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.

[0028] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to implement communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0029] In the context of this disclosure, the terms “carrier,” “component carrier (CC),” “band,” and “cell” are used interchangeably.

[0030] This disclosure focuses on carrier aggregation (CA), which offers greater flexibility and configurability.

[0031] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0032] Figure 1An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The communication environment 100 includes a first device 110 and a second device 120.

[0033] In some solutions, the second device 120 can provide one or more service areas for the first device 110. The service area provided by the second device 120 can be referred to as a cell. Figure 1 In the example, the second device 120 provides cell 102.

[0034] In some example embodiments, the first device 110 may be implemented as a terminal device or included in a terminal device, and the second device 120 may be implemented as a network device serving the terminal device or included in a network device serving the terminal device.

[0035] In the following description, for illustrative purposes, some example embodiments are described in which the first device 110 operates as a terminal device and the second device 120 operates as a network device. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the terminal device or other devices.

[0036] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device, the direction from the second device 120 to the first device 110 is referred to as the downlink (DL), and the direction from the first device 110 to the second device 120 is referred to as the uplink (UL). In the DL, the second device 120 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver).

[0037] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), 5.5G, and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0038] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it will be appreciated that one or more additional devices or apparatuses may be located in cell 102, and one or more additional cells may be deployed in communication environment 100.

[0039] Frequency domain resource combinations are discussed. Features such as Tx-Tx switching and low-band CA (LBCAsw) via switching are also discussed. These features represent solutions for specific frequency band combinations that pose challenges to the system due to the proximity of the bands, as described below.

[0040] Within the UE, there exists a hardware implementation that enables radio configurations to operate in different types of frequency bands. TDD can use band-specific filters and switches, while FDD can use duplex filters. Carrier aggregation (CA) may have established the need for switching between all these frequency bands, so TDD can be supported from CA switches, and FDD bands are also connected to switches, making them also suitable for TDD.

[0041] The table below lists some 5G frequency bands used for start and stop frequencies, including 5G type (FDD / TDD / Supplemental Downlink (SDL) / Supplemental Uplink (SUL)), direction / Dir (UL / DL / Bidirectional / BI), identifier / ID (dup / spec)).

[0042] Table of 5G Frequency Range 1 (FR1) band

[0043]

[0044] Observations from the "Identifier" column include: -n28 and n83 are the same uplink band. Declaring n28 for uplink-only operation is the same as declaring n83. (This is the same for n5 / n89, n82 / n91 / n92, n8 / n81 / n93 / n94;) - The bidirectional nature of the n50 and n51 bands means that the following bands only support DL (n50 and n51 are always switched to DL) [n75, n92, n94, n109] and [n76, n91, n93]; -n24=n255; - The TDD band can be SUL, or n40 / n97.

[0045] In some solutions, several modes of carrier operation in CA may have been defined using annotations and UE capabilities, as shown below.

[0046] - Applicable to UEs that support inter-band carrier aggregation with forced simultaneous Rx / Tx capability; - Applicable when performing dynamic Tx switching. DL interrupt requirement; - Only applicable to UEs that support inter-band carrier aggregation but do not have simultaneous Rx / Tx. The same restriction may apply when the applicable NR CA configuration is part of a higher-order configuration; - If the UE is configured with both NR UL carrier and NR SUL carrier in the cell, the handover time between the NR UL carrier and the NR SUL carrier can be 0µs; - For UEs that support SUL band combinations, Rx / Tx capability can be mandatory.

[0047] The above annotations may refer to addressing schemes for activities involving uplink / downlink (Rx / Tx) or carrier switching between uplink carriers (Tx handover), including some requirements for handover time. To link these operating modes to individual carriers, they may need to exist in certain dedicated UE capability groups, such as ULTxSwitchingBandPair, for mapping carriers of frequency band combinations to features of ULTxSwitching. If this feature mapping continues, there will be so many capabilities defining handover patterns or time-domain patterns that configurations begin to overlap between features, which is relevant.

[0048] However, in this disclosure, all time-divisions of resources can be provided as separate capabilities, such as support for Tx-Tx switching only between a pair of Tx-Tx. There is no Rx-Rx switching, and Tx-Rx switching only works currently—also as a special one-off solution to cover special cases.

[0049] The table for the 5G FR1 band may not easily disclose the combination issues, but upon closer inspection, it can be found that the combination of n12 and n29 is problematic due to insufficient frequency separation as shown in the table below.

[0050] Table of CA_n12-n29

[0051] This seems like an easy combination to support since the two frequency bands don't overlap, but that's not the case. Issues like this might require significant analysis and protocols within 3GPP, as the n12 UL will cause interference in the n29 DL because the duplex filter cannot suppress the uplink. In 5G, this might require research and protocols to identify solutions. Providing a time structure allocation could easily specify the handover operation between the n12 UL / DL and the n29 DL in a pattern suitable for avoiding interference.

[0052] An investigation into similar issues with CA_n5-n29 5G concluded that the operation is problematic, not due to duplex issues, but rather due to the (relatively) large carrier distance. The combinations and frequencies are shown in the table below.

[0053] Table of CA_n5-n29

[0054] Switching one frequency band at a time in the same manner as CA_n12-n29 can fix this UE issue. Similarly, the timing structure allocation will easily specify the handover operation between n5 UL / DL and n29 DL in a pattern suitable for avoiding antenna tuning problems.

[0055] There may be annotations and special UE capabilities that allow switching in a certain way, which is a suboptimal approach. However, implementing such features complicates the implementation and incurs overhead.

[0056] If the carrier is given a unique pattern and timing structure, then any operational conflicts and special requirements may already be managed in the configuration.

[0057] In this disclosure, a problem with a distributed time structure is proposed, which defines the operation of carriers within a frequency band combination based on a feature set.

[0058] It is permissible to configure a DL frequency range (DL of the band) with a UL frequency range (UL of the band). Therefore, any range can be combined. As mentioned above, some of these combinations may require unique operating modes, such as a combination of two carriers with mandatory requirements for simultaneous Rx / Tx operation. For TDD-TDD combinations, this may mean they are out of sync in the frame structure, while an FDD or SDL combination with a TDD band means that a TDD uplink can occur during the downlink of another carrier, and an FDD band can have an uplink during the TDD downlink. The table below shows some combinations of the two CA combinations.

[0059] Table of some 2CA combinations that force simultaneous Rx / Tx operations

[0060] The column for allowing DL interruptions defines whether the DL operation of the active carrier is allowed or interrupted when another configured carrier begins uplink operations, based on some of these band combinations for simultaneous Rx / Tx. DL operations marked "No" must be retained, while DL operations without comments are allowed to have interruptions in the DL. This can significantly influence the downlink operation pattern based on uplink activity.

[0061] Examples of time multiplexing between carriers as suggested in this disclosure are shown in Figure 2A As shown, multiple restrictive operations are combined.

[0062] Figure 2A An example of carrier scheduling for a shared scheduling solution with all Rx-Rx, Rx-Tx, and Tx-Tx restrictions for a device using CA_n5A-n29A-n41A-n66A (which the UE does not actually support) is shown, where ULTxSwitching single carriers n5, n41, n66, and Rx are switched on n5 and n29, and finally Tx-Rx is switched on n5, n29, and n41.

[0063] from Figure 2A As can be seen, this example illustrates a device supporting one Tx time slot for the uplink at a time. Therefore, whenever a Tx exists, only one carrier can be allowed to transmit. Furthermore, there may be limitations between Rx and Tx on n5 and n29. If n5 is transmitting, n29 may not be receiving, and vice versa. There may also be Rx-Rx limitations between n5 and n29. This could mean that while reception is occurring on one carrier, reception is not occurring on the other, and vice versa. This pattern can be repeated indefinitely. These are indicated by arrows.

[0064] Rx and / or Tx transitions may occur between time slots 5 and 6, between time slots 7 and 8, and again between time slot 10 of a pattern period and time slot 1 of a subsequent pattern period. These are indicated by black arrows.

[0065] from Figure 2A It is also clear that pairing of UL and DL carriers across the operating band can be easily supported without defining a complex new CA structure. This can be embedded in the operating pattern.

[0066] This disclosure may also suggest alternative approaches to achieving consensus on device capabilities. It may still be necessary to understand the combinations of carriers that the device can receive or transmit in parallel. However, within these different combinations, it may be necessary to understand the limitations of devices that can simultaneously transmit UL carriers and DL carriers. Figure 2A One of the capabilities coupled in a solution could be: Tx handover due to CA combination restrictions to extend UL services between carriers; Tx handover to create other power levels; simultaneous Rx / Tx capabilities, complying with UE restrictions; Rx / Rx handover while still utilizing the Rx band, complying with CA restrictions on the UE side; and configurations that must be allowed to exceed CA capabilities, where the network is responsible for complying with UE capabilities at each point in time.

[0067] Finally, this might be because the above example actually requires configuration for all frequency bands, including CA_n5-n29-n41-n66 in DL. Figure 2A Above the time slots are listed: CA_n5-n41-n66 DL and n5 UL; CA_n29-n41-n66 DL and n41 UL; CA_n29-n41-n66 DL and n66 UL.

[0068] In this way, the need for the NW to use RRC configuration to allocate and change carrier configurations can be greatly relaxed, because the NW can construct CA combinations and switch between carriers beyond what the UE supports, which would never be the case in current technology. Handover can replace RRC reconfiguration to change carrier allocations and determine when carriers can be scheduled.

[0069] The carrier can still be activated or deactivated to conserve power for monitoring the Physical Downlink Control Channel (PDCCH) / Downlink Control Information (DCI), and if deactivated, the network can still ensure adequate uplink and downlink scheduling given the handover table. If the carrier is deactivated, the carrier line in the handover table may become invalid.

[0070] The pattern configuration used for ULTxSwitching in this disclosure can be more generally replaced by Tx-Tx switching, and Rx-Tx switching between carriers can support LBCAsw uplink aspects as well as simultaneous Rx / Tx features.

[0071] Resource aggregation pattern configuration can eliminate these “special case” handover capabilities and elevate operation to a more general relationship between two carriers in Rx-Rx, Tx-Tx, and Rx-Tx, which is also easier to define from the UE’s perspective, regardless of whether it is used for features such as LBCAsw or the more general capabilities outlined in this disclosure.

[0072] The requirements and tests can remain the same. The concept allows for configuration switching based solely on the handover table, meaning the UE must still meet the requirements associated with each concurrent active state of the CA. Similarly, handover time may not depend on which carriers are being switched. Some UEs may be faster than others, therefore NW only needs to meet the UE capability reports for switching Rx-Rx, Tx-Tx, and Rx-Tx.

[0073] Another objective of this feature is to address Maximum Sensitivity Degradation (MSD), which is UE conflict caused by carriers using different frequency bands. The four cases of UL harmonics, harmonic mixing, cross-band isolation, and intermodulation still exist and are effective; however, pattern allocation allows the NW to control when a mechanism might occur. The tables below for UL harmonics, harmonic mixing, and intermodulation show several registered MSD relaxations for the combinations mentioned above.

[0074] Table for UL harmonics

[0075] Used for harmonic mixers

[0076] Tables for inter-switching

[0077] The table for UL harmonics shows that when n5 has an uplink, n41 DL may lose up to 10 dB of reference sensitivity (Refsens). The table for harmonic mixing shows that when n41 has an uplink, n5DL may lose up to 24 dB of Refsens. The table for intermodulation is for at least two CC uplinks. When the black box is found, it can indicate non-contiguous in-band uplink carrier aggregation (NC ULCA) (two CCs in the same frequency band).

[0078] According to some example embodiments of this disclosure, it may not have two ULCAs, and thus the second-order intermodulation distortion (IMD2) problem, particularly CA_n5-n41-n66, can be completely avoided.

[0079] exist Figure 2B In the updated pattern, the uplink harmonic self-interference issue may have been resolved. This can be indicated by clearing the slot activity using red. Note that this may only be necessary if the NW has overlapping frequency regions, so if the uplink frequency n5 multiplied by 3 is not equal to the DL frequency n41, the NW may not need to consider the handover pattern. The NW can report the inter-frame handover resource aggregation pattern (FIG.2A and FIG.2B) relative to the UE power headroom (PHR) on band n5. If a high PHR exists, the UE may be far from its maximum output power, and therefore DL interference may not exist. As the PHR decreases, the NW can be configured... Figure 2B The mode ensures n41 DL time slots at the cost of n5 UL time slots. A trade-off can be used at NW, so if UL resources are required, n41DL can simply not be activated in UL n5 time slots.

[0080] The following will refer to Figure 3 Let's discuss more details about the example process above. Figure 3 Signaling stream 300 for communication according to some embodiments of this disclosure is shown. Reference will be made to this document for discussion purposes. Figure 1 For example, signaling flow 300 can be discussed by using the first device 110 and the second device 120.

[0081] In the following example embodiments, frequency domain resources can refer to any suitable frequency resource. In one example, a frequency domain resource can be a component carrier (CC) or a CC with a single direction (such as UL CC or DL ​​CC). In another example, a frequency domain resource can be a frequency band / carrier, or a frequency band / carrier with a single direction (such as a UL band or DL ​​band). In other examples, frequency domain resources can also be represented in other suitable ways.

[0082] Furthermore, in the following example embodiments, time-domain resources can refer to any suitable time resource, such as duration, time window, etc. In one example, a time-domain resource may include at least one time slot. In another example, a time-domain resource may include at least one subframe. In yet another example, a time-domain resource may include at least one (OFDM) symbol. In other examples, time-domain resources may also be represented in other suitable ways.

[0083] According to some embodiments of this disclosure, the first device 110 can provide capability-related information to the second device 120. Using the capability-related information, the second device 120 can provide appropriate configurations / commands to the first device 110. An example capability-related information reporting process will be discussed below.

[0084] like Figure 3 As shown, the first device 110 can send (310-1) capability-related information to the second device 120, and the second device 120 can receive (310-2) capability-related information accordingly.

[0085] In some example embodiments, capability-related information can indicate handover-related capabilities between different frequency domain resources. In one example, handover-related capabilities may include whether the first device 110 supports handover from an uplink frequency domain resource to another uplink frequency domain resource (such as a Tx-Tx handover), and / or the duration required for the first device 110 to handover from an uplink frequency domain resource to another uplink frequency domain resource. In another example, handover-related capabilities may include whether the first device 110 supports handover from a downlink frequency domain resource to an uplink frequency domain resource (such as an Rx-Tx handover), and / or the duration required for the first device 110 to handover from a downlink frequency domain resource to an uplink frequency domain resource. In yet another example, handover-related capabilities may include whether the first device 110 supports handover from an uplink frequency domain resource to a downlink frequency domain resource (such as a Tx-Rx handover), and / or the duration required for the first device 110 to handover from an uplink frequency domain resource to a downlink frequency domain resource. In yet another example, handover-related capabilities may include whether the first device 110 supports handover from one downlink frequency domain resource to another (such as Rx-Rx handover), and / or the duration required for the first device 110 to handover from one downlink frequency domain resource to another. It should be noted that in other examples, the first device 110 may also report other handover-related capabilities.

[0086] Alternatively or additionally, in some example embodiments, capability-related information may be indicated by a resource aggregation pattern (such as, supported by the first device 110) Figure 2A / Figure 2B The maximum number of frequency domain resources associated with the resource aggregation pattern shown. Specifically, the maximum number of frequency domain resources associated with the resource aggregation pattern supported by the first device 110 is different from the maximum number of frequency domain resources simultaneously activated at the first device 110. Specifically, the former is greater than the latter.

[0087] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include a first maximum number of uplink and downlink frequency domain resources associated with the resource aggregation pattern supported by the first device 110. Alternatively or additionally, in some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include a second maximum number of uplink frequency domain resources associated with the resource aggregation pattern supported by the first device 110. Alternatively or additionally, in some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include a third maximum number of downlink frequency domain resources associated with the resource aggregation pattern supported by the first device 110.

[0088] Alternatively or additionally, in some example embodiments, capability-related information may indicate whether the first device 110 supports different resource aggregation patterns (e.g., in...). Figure 2A and Figure 2B (Switching between). Alternatively or additionally, in some example embodiments, capability-related information may indicate the maximum number of resource aggregation patterns configured by the first device 110.

[0089] It should be noted that in other examples, other capability-related capabilities may also be provided by the first device 110.

[0090] Based at least in part on capability-related information, the second device 120 can determine (320) at least one resource aggregation pattern (such as one or more resource aggregation patterns). Details regarding the resource aggregation pattern and how the second device determines the resource aggregation pattern based on capability-related information will be discussed below.

[0091] In some example embodiments, the resource aggregation pattern can be associated with a set of frequency domain resources (in... Figure 2A In the example, n5A-n29A-n41A-n66A) are associated. Specifically, a resource aggregation pattern may include at least one sub-pattern, and different sub-patterns correspond to different subsets of the frequency domain resources and different time domain resources. For better understanding, refer to... Figure 2A ,in Figure 2A An example of a resource aggregation pattern is shown, which includes subpatterns 210, 220 and 230, wherein subpattern 210 corresponds to the subset of {DL: n5-n41-n66, UL: n5} and time slots 1-5, subpattern 220 corresponds to the subset of {n29-n41-n66, UL: n41, UL: n5} and time slots 6 and 7, and subpattern 230 corresponds to the subset of {n29-n41-n66, UL: n66} and time slots 8-10.

[0092] In some example embodiments, the resource aggregation pattern determined by the second device 120 may need to satisfy one or more requirements. In one example, the resource aggregation pattern may satisfy requirements related to capability information. For example, based on handover-related capabilities, the second device 120 may determine at least one uplink frequency domain resource and / or at least one downlink frequency domain resource. Alternatively or additionally, in another example, the resource aggregation pattern may satisfy requirements for a set of predefined handover rules (such as handover rules specified as annotations in the radio standard). Alternatively or additionally, in yet another example, the resource aggregation pattern may satisfy requirements for maximum sensitivity degradation (MSD). In other examples, other requirements may also be used to define a suitable resource aggregation pattern.

[0093] As discussed, the resource aggregation pattern is associated with a set of frequency domain resources. When determining this set of frequency domain resources, the second device 120 needs to follow at least one rule. One example rule is that the number of frequency domain resources included in the set is less than or equal to the first maximum number discussed above, but is allowed to be greater than the maximum number of frequency domain resources supported to be simultaneously active at the first device 110. Another example rule is that the number of uplink frequency domain resources included in the set is less than or equal to a second maximum number, but is allowed to be greater than the maximum number of uplink frequency domain resources supported to be simultaneously active at the first device 110. Yet another example rule is that the number of downlink frequency domain resources included in the set is less than or equal to a third maximum number, but is allowed to be greater than the maximum number of downlink frequency domain resources supported to be simultaneously active at the first device 110.

[0094] After determining at least one resource aggregation pattern, the second device 120 may send (330-1) configuration information indicating at least one resource aggregation pattern to the first device 110, and the first device 110 may receive (330-2) the configuration information accordingly.

[0095] In some example embodiments, the configuration information may indicate at least one uplink frequency domain resource included in the group of frequency domain resources, and / or at least one downlink frequency domain resource included in the group of frequency domain resources. Alternatively or additionally, in some example embodiments, the configuration information may indicate at least one sub-pattern, which may be represented by any suitable parameters.

[0096] Alternatively or additionally, in some example embodiments, the configuration information may indicate at least one subset of the set of frequency domain resources corresponding to at least one subpattern, and / or at least one verification time window corresponding to at least one subpattern.

[0097] Alternatively or additionally, in some exemplary embodiments, the configuration information may indicate at least one switching condition between different subpatterns and / or at least one switching condition between different resource aggregation patterns, which may be represented as at least one threshold related to inference, MSD, flow status, power margin status, etc.

[0098] It should be noted that the configuration information may include any parameters / information related to the resource aggregation pattern(s) and / or execution information related to the resource aggregation pattern(s).

[0099] It should also be noted that configuration information can be included in one or more messages / signaling. As an example, when a PCell is activated, part of the configuration information can be included in the signaling, such as the frequency domain resources of (multiple) resource aggregation patterns that can be configured. Another part of the configuration information can be included in the following (multiple) RRC signaling, such as the format information of the resource aggregation pattern, (multiple) switching / update conditions between different subpatterns, and switching / update conditions between different resource aggregation patterns, etc.

[0100] As an example, the first message may include information about at least one uplink frequency domain resource and at least one downlink frequency domain resource, and the second message may include information about at least one of the following: at least one subpattern, at least one switching condition, at least one subset of the set of frequency domain resources, or at least one verification time window.

[0101] In some example embodiments, for each frequency domain resource, the configuration information may also indicate at least one of the following: the multiplexing type of the frequency domain resource (such as TDD or FDD), the transmission direction of the frequency domain resource (such as UL, DL, or BI), or the maximum transmission power of the frequency domain resource.

[0102] Based on the configuration information, the first device 110 and the second device 120 can communicate with each other (340).

[0103] According to some example embodiments, the first device 110 can be switched between different sub-patterns (e.g., in...). Figure 2A In the example, communication with the second device 120 involves switching between subpatterns 210, 220, and 230. Furthermore, the first device 110 and / or the second device 120 can update the current subpattern to a different subpattern. Such an example process will be discussed below.

[0104] In some cases, at least one subpattern includes a first subpattern and a second subpattern. In this case, the first device 110 can use the first subpattern to communicate with the second device 120. The first device can then switch (360) the first subpattern to the second subpattern based on configuration information. In some cases, the first subpattern can be switched to the second subpattern by at least one of the following: switching uplink frequency domain resources of the first subpattern to another uplink frequency domain resource of the second subpattern, switching downlink frequency domain resources of the first subpattern to an uplink frequency domain resource of the second subpattern, switching uplink frequency domain resources of the first subpattern to another downlink frequency domain resource of the second subpattern, or switching downlink frequency domain resources of the first subpattern to another downlink frequency domain resource of the second subpattern.

[0105] Generally, frequency domain resources can be configured and activated by the second device 120. When the frequency domain resources are active, the first device 110 can use the frequency domain resources to communicate with the second device 120.

[0106] In some cases, the first device 110 may not activate all configured frequency domain resources at once, except when receiving an explicit instruction from the second device 120. In one example, if the configuration information includes an instruction for the first device 110 to activate all frequency domain resources included in that group of frequency domain resources, then all frequency domain resources are activated, meaning that after receiving the configuration information, the first device 110 can use any activated frequency domain resource as needed.

[0107] In some other cases, the second device 120 may activate frequency domain resources after sending configuration information. In some example embodiments, in response to receiving configuration information, the first device 110 is configured with a set of frequency domain resources, and then one or more frequency domain resources in that set can be activated by an activation command from the second device 120. Thereafter, the first device 110 can perform communication with the second device 120, at least in part, based on the configuration information, using one or more activated frequency domain resources.

[0108] In some cases, to save power, one or more frequency domain resources may also be deactivated. In some example embodiments, the second device 120 may send a message to the first device 110 for deactivating a frequency domain resource in a set of frequency domain resources. If so, upon receiving the message, the first device 110 may assume that the information related to the deactivated frequency domain resources included in the configuration information is empty. For example, in Figure 2A In the example, if n29 is deactivated, then Figure 2A The corresponding line in the text is considered empty.

[0109] According to some example embodiments, the second device 120 can update the resource aggregation pattern. Such example embodiments will be discussed below.

[0110] As an example, the second device 120 may send (350-1) a message to the first device 110 for updating the resource aggregation pattern, and the first device 110 may accordingly receive (350-2) the message. Specifically, in some cases, the message may be used to incorporate at least one new frequency domain resource into a group of frequency domain resources. In one example, the first device 110 may perform measurements on the frequency domain resources and report the measurement results to the second device 120. The second device 120 may incorporate a new frequency domain resource only if the measurement results indicate that the frequency domain resource is available.

[0111] Alternatively or additionally, in some cases, the message can be used to exclude at least one frequency domain resource from a set of frequency domain resources. Alternatively or additionally, in some cases, the message can be used to invalidate at least one time-frequency resource in a resource aggregation pattern. As an example, in Figure 2B In the example, at least one time-frequency resource 250 and at least one time-frequency resource 260 are invalid.

[0112] In some example embodiments, the first device 110 may also trigger an update of the resource aggregation pattern. In one example, based on determining that at least one update condition is met, the first device 110 may update the resource aggregation pattern by invalidating at least one time-frequency resource of the resource aggregation pattern. In some example embodiments, the at least one update condition may be associated with at least one of the following: inference state at the first device 110, power margin state at the first device 110, or maximum sensitivity degradation (MSD) state at the first device 110. In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, cross-band isolation, and intermodulation.

[0113] Then, the first device 110 also needs to notify the second device 120 of the update status. Specifically, the first device 110 may send message 370 to the second device, and the second device 120 may receive message (370-2) accordingly. Specifically, the message may indicate at least one of the following: an updated resource aggregation pattern, or a reason for the update (e.g., due to inference status, MSD, power margin, etc.).

[0114] In summary, the second device 120 can configure a resource aggregation pattern to the first device 110. The resource aggregation pattern can be updated to another resource aggregation pattern. Furthermore, the update of the resource aggregation pattern can be triggered under specific conditions, and either the first device 110 or the second device 120 can trigger the update.

[0115] As described above, the first device 110 may have the ability to switch between different resource aggregation patterns, and / or the first device 110 supports the configuration of more than one resource aggregation pattern (the maximum number of resource aggregation patterns supported by the first device 110 is greater than one). In this case, the first device 110 can switch between different resource aggregation patterns. Referring below... Figure 3 This section discusses example implementations for switching between different resource aggregation patterns.

[0116] In some embodiments, the second device 120 sends (330-1) configuration information indicating a plurality of resource aggregation patterns. In some cases, the first device 110 may determine a resource aggregation pattern from the plurality of resource aggregation patterns based on an instruction from the second device 120, which indicates the resource aggregation pattern to be applied from the plurality of resource aggregation patterns. That is, the second device 120 instructs the first device 110 which resource aggregation pattern to apply.

[0117] In some example embodiments, the second device 120 may determine the resource aggregation pattern to be applied based on at least one condition. In one example, the at least one condition may be associated with the verification duration, such as pattern #1 being configured for frame #1, pattern #2 being configured for frame #2, etc. In another example, the at least one condition may be associated with the inference state at the first device 110. In yet another example, the at least one condition may be associated with the power margin state of the first device 110. In yet another example, the at least one condition may be associated with the maximum sensitivity degradation (MSD) state at the first device 110. In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, cross-band isolation, and intermodulation.

[0118] In some example embodiments, in response to the fulfillment of a first condition corresponding to the first resource aggregation pattern, the second device 120 may send a message to the first device 110 instructing the first device 110 to switch to applying the first resource aggregation pattern.

[0119] Alternatively, in some cases, the first device 110 may determine a resource aggregation pattern from a plurality of resource aggregation patterns based on at least one condition for applying the resource aggregation pattern among a plurality of resource aggregation patterns. In this case, the second device 120 may send at least one condition to the first device 110.

[0120] In some example embodiments, in response to the satisfaction of a first condition corresponding to the first resource aggregation pattern, the second device 120 may send an indication to the first device 110 that the first condition has been satisfied. The second device 120 may determine whether to apply the first resource aggregation pattern. Then, the second device 120 may send a (350-1) message to the first device 110, which instructs the first device 110 to switch to applying the first resource aggregation pattern.

[0121] In some example embodiments, in response to the fulfillment of a first condition corresponding to the first resource aggregation pattern, the first device 110 may switch (360) to apply the first resource aggregation pattern. The first device 110 may then send a (370-1) message to the second device 120, wherein the message indicates at least one of the following: the first device 110 has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern. In this way, the second device 120 can understand the switch at the first device 110.

[0122] For better understanding, reference will be provided. Figure 4 Discuss more example implementations, Figure 4 An example signaling flow 400 for communication is shown according to some example embodiments of this disclosure. Figure 4 In the example, the UE is used as an example of the first device 110, and the network is used as an example of the second device 120.

[0123] In step 1, the UE can provide the network with UE capabilities, i.e., capability-related information as described above. In one example, the UE can indicate the supported DL and UL band combinations. Additionally, the UE can indicate support for the following: Rx-Rx handover (optionally, handover time), Rx-Tx handover (optionally, handover time), and Tx-Tx handover (optionally, handover time). Alternatively or additionally, the UE can indicate whether the first device supports dynamically changing the handover table, the maximum number of carriers the UE can support, and the number of handover table / resource aggregation patterns the UE can support.

[0124] In step 2, the PCell can be activated. During PCell activation, the UE and PCell can exchange multiple messages. In some example embodiments, the PCell can configure frequency domain resources for the UE. It should be noted that any appropriate information can be provided / configured to the UE.

[0125] In the following steps, the network can determine the resource aggregation pattern. In step 4, the network can establish which DL carriers can be part of the UE configuration. This may exceed the UE CA DL capability, which may subsequently be switched by Rx-Rx. In step 5, the network can establish which UL carriers can be part of the UE configuration. This may exceed the UE CA UL capability, which may subsequently be switched by Tx-Tx. In step 6, the network will determine if there are DL and UL conflicts, as given by the UE capabilities. If so, the network will resolve these conflicts with the Rx-Tx handover. In step 7, the network can evaluate the desired Tx and Rx patterns and determine if there are conflicts that will lead to MSD. If so, the network can avoid such conflicts (such as...) by canceling Rx or Tx during the conflict. Figure 2B Alternatively, the network can establish multiple patterns, where the PHR or Tx used depends on the MSD. If it is above a certain threshold, a pattern that maintains Tx can be used, and if it is below a certain threshold, a pattern that cancels Rx or Tx can be used. It should be noted that steps 4 through 7 can be performed in any suitable order and can be performed individually or in combination. Furthermore, any one of steps 4 through 7 is optional.

[0126] In step 8, the UE is reconfigured for the superset of DL and UL carriers and the handover configuration(s) (i.e., resource aggregation patterns). In step 9, the PCell can send the RRC configuration (configuration information as described above) to the UE. In one example, the RRC configuration can indicate the time multiplexing of DL channel / carrier, UL channel / carrier, and all carrier patterns (i.e., resource aggregation patterns). Furthermore, if there is more than one pattern, the RRC configuration also indicates the criteria for when and how the RRC configuration is used.

[0127] In step 10, the UE can store and prepare configurations. Furthermore, for all configured carriers, it may not all be activated at once, except when an RRC configuration indication is explicitly used. In step 11, if more RRC configurations are configured, the UE can configure the conditions for when to use which handover table. Alternatively, the UE can receive explicit commands indicating resource aggregation patterns to be applied by lower layers.

[0128] Figure 5 A flowchart of an example method 500 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 500 is described by the angle of the first device 110 in the middle.

[0129] At block 510, the first device receives configuration information from the second device, which indicates a resource aggregation pattern associated with a set of frequency domain resources. The resource aggregation pattern includes at least one sub-pattern, with different sub-patterns corresponding to different subsets of the set of frequency domain resources and different time domain resources.

[0130] In box 520, the first device performs communication with the second device based on the configuration information.

[0131] In some example embodiments, the number of frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of frequency domain resources simultaneously activated and supported at the first device, and / or the number of uplink frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of uplink frequency domain resources simultaneously activated and supported at the first device, and / or the number of downlink frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of downlink frequency domain resources simultaneously activated and supported at the first device.

[0132] In some example embodiments, the configuration information may indicate at least one of the following: at least one uplink frequency domain resource in a set of frequency domain resources, at least one downlink frequency domain resource in a set of frequency domain resources, at least one subpattern, at least one switching condition between different subpatterns, at least one subset of a set of frequency domain resources corresponding to at least one subpattern, or at least one verification time window corresponding to at least one subpattern.

[0133] In some example embodiments, the first message may include information about at least one uplink frequency domain resource and at least one downlink frequency domain resource, and the second message may include information about at least one of the following: at least one subpattern, at least one switching condition, at least one subset of the set of frequency domain resources, or at least one verification time window.

[0134] In some example embodiments, method 500 may further include: communicating with a second device using a first sub-pattern; and switching the first sub-pattern to a second sub-pattern based on configuration information by at least one of the following: switching uplink frequency domain resources of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern, switching downlink frequency domain resources of the first sub-pattern to uplink frequency domain resources of the second sub-pattern, switching uplink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, and switching downlink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

[0135] In some example embodiments, if the configuration information includes an indication that the first device should activate all frequency domain resources included in a set of frequency domain resources, then all frequency domain resources can be activated.

[0136] In some example embodiments, method 500 may further include: performing communication with the second device, at least in part based on configuration information, by using one or more frequency domain resources.

[0137] In some example embodiments, method 500 may further include: receiving from a second device a message for deactivating frequency domain resources in the group of frequency domain resources; and assuming that information related to the deactivated frequency domain resources included in the configuration information is invalid.

[0138] In some example embodiments, method 500 may further include: receiving a message from a second means for updating a resource aggregation pattern, wherein the message is used for at least one of the following: incorporating at least one new frequency domain resource into the group of frequency domain resources, excluding at least one frequency domain resource from the group of frequency domain resources, or invalidating at least one time-frequency resource of the resource aggregation pattern.

[0139] In some example embodiments, method 500 may further include: updating a resource aggregation pattern by invalidating at least one time-frequency resource of the resource aggregation pattern based on determining that at least one update condition is met; and sending a message to a second device indicating at least one of the following: the updated resource aggregation pattern or the reason for the update.

[0140] In some example embodiments, at least one update condition may be associated with at least one of the following: the inference state at the first device, the power margin state of the first device, or the maximum sensitivity degradation (MSD) state at the first device.

[0141] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0142] In some example embodiments, method 500 may further include: sending capability-related information to a second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0143] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0144] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0145] In some example embodiments, for each frequency domain resource, the configuration information may also indicate at least one of the following: the multiplexing type of the frequency domain resource, the transmission direction of the frequency domain resource, or the maximum transmission power of the frequency domain resource.

[0146] In some example embodiments, frequency domain resources may be component carriers (CC), or frequency bands, or CCs or frequency bands with a single direction, and time domain resources may include at least one time slot, or at least one subframe, or at least one symbol.

[0147] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0148] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0149] Figure 6 A flowchart of an example method 600 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 600 is described by the angle of the second device 120 in the middle.

[0150] At box 610, the second device sends configuration information to the first device, which indicates a resource aggregation pattern associated with a set of frequency domain resources. The resource aggregation pattern includes at least one sub-pattern, and different sub-patterns correspond to different subsets of the set of frequency domain resources and different time domain resources.

[0151] In box 620, the second device performs communication with the first device based on the configuration information.

[0152] In some example embodiments, method 600 may further include: receiving capability-related information from a first device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; and determining configuration information based at least in part on the capability-related information.

[0153] In some example embodiments, the maximum number of frequency domain resources associated with the resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with the resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with the resource aggregation pattern supported by the first device, and a third maximum number of downlink frequency domain resources associated with the resource aggregation pattern supported by the first device.

[0154] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0155] In some example embodiments, the resource aggregation pattern may satisfy at least one of the following: requirements for capability-related information, requirements for a set of predefined switching rules, or requirements for maximum sensitivity degradation (MSD).

[0156] In some example embodiments, method 600 may further include: determining a set of frequency domain resources associated with a resource aggregation pattern, wherein the number of frequency domain resources included in the set of frequency domain resources is less than or equal to a first maximum number and is permitted to be greater than a maximum number of frequency domain resources simultaneously active at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than or equal to a second maximum number and is permitted to be greater than a maximum number of uplink frequency domain resources simultaneously active at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than or equal to a third maximum number and is permitted to be greater than a maximum number of downlink frequency domain resources simultaneously active at the first device.

[0157] In some example embodiments, the configuration information may indicate at least one of the following: at least one uplink frequency domain resource included in a set of frequency domain resources, at least one downlink frequency domain resource included in a set of frequency domain resources, at least one subpattern, at least one switching condition between different subpatterns, at least one subset of a set of frequency domain resources corresponding to at least one subpattern, or at least one verification time window corresponding to at least one subpattern.

[0158] In some example embodiments, the first message may include information about at least one uplink frequency domain resource and at least one downlink frequency domain resource, and the second message may include information about at least one of the following: at least one subpattern, at least one switching condition, at least one subset of the set of frequency domain resources, or at least one verification time window.

[0159] In some example embodiments, the configuration information may include an instruction to the first device to activate all frequency domain resources included in the group of frequency domain resources.

[0160] In some example embodiments, method 600 may further include: sending a message for updating a resource aggregation pattern to a first device based on determining that at least one update condition is met, wherein the message is used for at least one of the following: incorporating at least one new frequency domain resource into the group of frequency domain resources, excluding at least one frequency domain resource from the group of frequency domain resources, or invalidating at least one time-frequency resource of the resource aggregation pattern.

[0161] In some example embodiments, at least one update condition may be associated with at least one of the following: the inference state at the first device, the power margin state of the first device, or the maximum sensitivity degradation (MSD) state at the first device.

[0162] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0163] In some example embodiments, method 600 may further include: receiving a message from a first device indicating at least one of the following: the resource aggregation pattern is updated by the first device by invalidating at least one time-frequency resource of the resource aggregation pattern, the updated resource aggregation pattern, or the reason for the update.

[0164] In some example embodiments, for each frequency domain resource, the configuration information may also indicate at least one of the following: the multiplexing type of the frequency domain resource, the transmission direction of the frequency domain resource, or the maximum transmission power of the frequency domain resource.

[0165] In some example embodiments, frequency domain resources may be component carriers (CC), or frequency bands, or CCs with a single direction, or frequency bands with a single direction, and time domain resources may include at least one time slot, or at least one subframe, or at least one symbol.

[0166] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0167] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0168] Figure 7 A flowchart of an example method 700 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 700 is described by the angle of the first device 110 in the middle.

[0169] At frame 710, the first device receives configuration information from the second device, which indicates multiple resource aggregation patterns.

[0170] At block 720, the first device determines a resource aggregation pattern from a plurality of resource aggregation patterns based on at least one of the following: at least one condition for applying the resource aggregation pattern from the plurality of resource aggregation patterns, or an instruction from the second device indicating the resource aggregation pattern to be applied from the plurality of resource aggregation patterns, wherein each resource aggregation pattern is associated with a set of frequency domain resources, and wherein the number of frequency domain resources included in the set of frequency domain resources is less than a first maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active frequency domain resources supported at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than a second maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active uplink frequency domain resources supported at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than a third maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active downlink frequency domain resources supported at the first device.

[0171] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0172] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0173] In some example embodiments, method 700 may further include: sending an indication that the first condition has been met to a second device in response to the first condition corresponding to the first resource aggregation pattern being met; and receiving a message from the second device that instructs the first device to switch to applying the first resource aggregation pattern.

[0174] In some example embodiments, method 700 may further include: switching to apply the first resource aggregation pattern in response to a first condition corresponding to the first resource aggregation pattern being met; and sending a message to the second device indicating at least one of the following: the first device has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern.

[0175] In some example embodiments, method 700 may further include: sending capability-related information to a second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0176] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0177] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0178] In some example embodiments, the frequency domain resource may be a component carrier (CC), or a frequency band, or a CC with a single direction, or a frequency band with a single direction.

[0179] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0180] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0181] Figure 8 A flowchart of an example method 800 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 800 is described by the angle of the second device 120 in the middle.

[0182] In box 810, the second device sends configuration information to the first device, which indicates multiple resource aggregation patterns.

[0183] At block 820, the second device sends at least one of the following to the first device: at least one condition for applying a resource aggregation pattern from a plurality of resource aggregation patterns, or an instruction from the second device indicating a resource aggregation pattern to be applied from the plurality of resource aggregation patterns, wherein each resource aggregation pattern is associated with a set of frequency domain resource patterns, and wherein the number of frequency domain resources included in the set of frequency domain resources is permitted to be greater than the maximum number of frequency domain resources simultaneously active supported at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is permitted to be greater than the maximum number of uplink frequency domain resources simultaneously active supported at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is permitted to be greater than the maximum number of downlink frequency domain resources simultaneously active supported at the first device.

[0184] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0185] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0186] In some example embodiments, method 800 may further include: receiving from a first device an indication that a first condition corresponding to a first resource aggregation pattern has been met; and sending a message to the first device instructing the first device to switch to applying the first resource aggregation pattern.

[0187] In some example embodiments, method 800 may further include: in response to a first condition corresponding to a first resource aggregation pattern being met, sending a message to a first device that instructs the first device to switch to applying the first resource aggregation pattern.

[0188] In some example embodiments, method 800 may further include: receiving capability-related information from a first device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; and determining configuration information based at least in part on the capability-related information.

[0189] In some example embodiments, the frequency domain resource may be a component carrier (CC) or a frequency band, or a CC with a single direction, or a frequency band with a single direction.

[0190] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0191] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0192] Figure 9 A flowchart of an example method 900 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 The method 900 is described by the angle of the first device 110 in the middle.

[0193] In block 910, the first device sends capability-related information to the second device, which indicates at least one of the following: handover capability between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0194] In block 920, the first device receives configuration information from the second device indicating at least one resource aggregation pattern, which is determined by the second device based at least in part on capability-related information.

[0195] In some example embodiments, a resource aggregation pattern may be associated with a set of frequency domain resources, and wherein the resource aggregation pattern includes at least one sub-pattern, and different sub-patterns may correspond to different subsets of a set of frequency domain resources and different time domain resources.

[0196] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0197] In some example embodiments, a resource aggregation pattern may be associated with a set of frequency domain resources, wherein the number of frequency domain resources included in the set of frequency domain resources is less than a first maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active frequency domain resources supported at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than a second maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active uplink frequency domain resources supported at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than a third maximum number and is allowed to be greater than or equal to the maximum number of simultaneously active downlink frequency domain resources supported at the first device.

[0198] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, and the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0199] In some example embodiments, at least one resource aggregation pattern may include a first resource aggregation pattern associated with a first group of frequency domain resources, and the configuration information indicates at least one of the following: at least one uplink frequency domain resource included in the first group of frequency domain resources, at least one downlink frequency domain resource included in the first group of frequency domain resources, at least one first sub-pattern included in the first resource aggregation pattern, at least one switching condition between different first sub-patterns, at least one first subset of the first group of frequency domain resources corresponding to at least one first sub-pattern, or at least one first time domain resource corresponding to at least one first sub-pattern.

[0200] In some example embodiments, method 900 may further include: communicating with a second device using a first sub-pattern; and switching the first sub-pattern to a second sub-pattern based on configuration information by at least one of the following: switching uplink frequency domain resources of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern, switching downlink frequency domain resources of the first sub-pattern to uplink frequency domain resources of the second sub-pattern, switching uplink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, or switching downlink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

[0201] In some example embodiments, method 900 may further include: determining a resource aggregation pattern from at least one resource aggregation pattern based on at least one of the following: at least one condition for applying the resource aggregation pattern among a plurality of resource aggregation patterns, or an indication from a second device that indicates the resource aggregation pattern to be applied from the plurality of resource aggregation patterns.

[0202] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0203] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0204] In some example embodiments, method 900 may further include: sending an indication that the first condition has been met to a second device in response to the first condition corresponding to the first resource aggregation pattern being met; and receiving a message from the second device that instructs the first device to switch to applying the resource aggregation pattern.

[0205] In some example embodiments, method 900 may further include: switching to apply the first resource aggregation pattern in response to a first condition corresponding to the first resource aggregation pattern being met; and sending a message to the second device indicating at least one of the following: the first device has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern.

[0206] In some example embodiments, the frequency domain resource may be a component carrier (CC), or a frequency band, or a CC with a single direction, or a frequency band with a single direction.

[0207] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0208] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0209] Figure 10 A flowchart of an example method 1000 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1000 is described by the angle of the second device 120 in the middle.

[0210] In block 1010, the second device receives capability-related information from the first device, which indicates at least one of the following: handover capability between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of resource aggregation patterns configured by the first device, or the maximum number of frequency domain resources associated with resource aggregation patterns supported by the first device.

[0211] At box 1020, the second device determines at least one resource aggregation pattern based at least in part on capability-related information.

[0212] At frame 1030, the second device sends configuration information, including at least one resource aggregation pattern, to the first device.

[0213] In some example embodiments, the resource aggregation mode may satisfy at least one of the following: requirements for capability-related information, requirements for a set of predefined switching rules, or requirements for maximum sensitivity degradation (MSD).

[0214] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0215] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, and the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0216] In some example embodiments, method 1000 may further include: determining a set of frequency domain resources associated with a resource aggregation pattern, wherein the number of frequency domain resources included in the set of frequency domain resources is less than or equal to a first maximum number and is allowed to be greater than a maximum number of frequency domain resources simultaneously active at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than or equal to a second maximum number and is allowed to be greater than a maximum number of uplink frequency domain resources simultaneously active at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than or equal to a third maximum number and is allowed to be greater than a maximum number of downlink frequency domain resources simultaneously active at the first device.

[0217] In some example embodiments, a resource aggregation pattern may be associated with the set of frequency domain resources, and the resource aggregation pattern includes at least one sub-pattern, with different sub-patterns corresponding to different subsets of the set of frequency domain resources and different time domain resources.

[0218] In some example embodiments, at least one resource aggregation pattern may include a first resource aggregation pattern associated with a first group of frequency domain resources, and the configuration information indicates at least one of the following: at least one uplink frequency domain resource included in the first group of frequency domain resources, at least one downlink frequency domain resource included in the first group of frequency domain resources, at least one first sub-pattern included in the first resource aggregation pattern, at least one switching condition between different first sub-patterns, at least one first subset of the first group of frequency domain resources corresponding to at least one first sub-pattern, or at least one first time domain resource corresponding to at least one first sub-pattern.

[0219] In some example embodiments, the first device may support switching between different resource aggregation patterns, and the first device may support being configured with more than one resource aggregation pattern, and may also enable the first device to: send at least one of the following to the first device: at least one condition for applying a resource aggregation pattern among the multiple resource aggregation patterns, or an indication from the second device that indicates the resource aggregation pattern to be applied from the multiple resource aggregation patterns.

[0220] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0221] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0222] In some example embodiments, method 1000 may further include: receiving from a first device an indication that a first condition corresponding to a first resource aggregation pattern has been met; and sending a message to the first device instructing the first device to switch to applying the first resource aggregation pattern.

[0223] In some example embodiments, method 1000 may further include: in response to a first condition corresponding to a first resource aggregation pattern being met, sending a message to a first device that instructs the first device to switch to applying the first resource aggregation pattern.

[0224] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0225] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0226] In some example embodiments, a first means capable of performing any of the methods 500 (e.g., Figure 1 The first device 110 may include a component for performing the corresponding operation of method 500. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0227] In some example embodiments, the first device may include: a component for receiving configuration information from the second device, the configuration information indicating a resource aggregation pattern associated with a set of frequency domain resources, the resource aggregation pattern including at least one sub-pattern, different sub-patterns corresponding to different subsets of the set of frequency domain resources and different time domain resources; and a component for performing communication with the second device based on the configuration information.

[0228] In some example embodiments, the number of frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of frequency domain resources simultaneously activated and supported at the first device, and / or the number of uplink frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of uplink frequency domain resources simultaneously activated and supported at the first device, and / or the number of downlink frequency domain resources included in a set of frequency domain resources may be allowed to be greater than the maximum number of downlink frequency domain resources simultaneously activated and supported at the first device.

[0229] In some example embodiments, the configuration information may indicate at least one of the following: at least one uplink frequency domain resource included in a set of frequency domain resources, at least one downlink frequency domain resource included in a set of frequency domain resources, at least one subpattern, at least one switching condition between different subpatterns, at least one subset of a set of frequency domain resources corresponding to at least one subpattern, or at least one verification time window corresponding to at least one subpattern.

[0230] In some example embodiments, the first message may include information about at least one uplink frequency domain resource and at least one downlink frequency domain resource, and the second message may include information about at least one of the following: at least one subpattern, at least one switching condition, at least one subset of a set of frequency domain resources, or at least one verification time window.

[0231] In some example embodiments, the first device may further include: a component for communicating with the second device using a first sub-pattern; and a component for switching the first sub-pattern to the second sub-pattern based on configuration information by at least one of the following: switching uplink frequency domain resources of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern, switching downlink frequency domain resources of the first sub-pattern to uplink frequency domain resources of the second sub-pattern, switching uplink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, and switching downlink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

[0232] In some example embodiments, if the configuration information includes an indication that instructs the first device to activate all frequency domain resources included in a set of frequency domain resources, then all frequency domain resources can be activated.

[0233] In some example embodiments, the first device may further include a component for performing communication with the second device, at least in part based on configuration information, by using one or more frequency domain resources.

[0234] In some example embodiments, the first device may further include: a component for receiving a message from the second device for deactivating a frequency domain resource in a set of frequency domain resources; and a component for assuming that information included in the configuration information related to the deactivated frequency domain resource is invalid.

[0235] In some example embodiments, the first device may further include a component for receiving a message from the second device for updating a resource aggregation pattern, wherein the message is used for at least one of the following: incorporating at least one new frequency domain resource into a set of frequency domain resources, excluding at least one frequency domain resource from a set of frequency domain resources, or invalidating at least one time-frequency resource of the resource aggregation pattern.

[0236] In some example embodiments, the first device may further include: a component for updating a resource aggregation pattern by invalidating at least one time-frequency resource of the resource aggregation pattern based on determining that at least one update condition is met; and a component for sending a message to the second device, the message indicating at least one of the following: the updated resource aggregation pattern or the reason for the update.

[0237] In some example embodiments, at least one update condition may be associated with at least one of the following: the inference state at the first device, the power margin state of the first device, or the maximum sensitivity degradation (MSD) state at the first device.

[0238] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0239] In some example embodiments, the first device may further include a component for sending capability-related information to the second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0240] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0241] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0242] In some example embodiments, for each frequency domain resource, the configuration information may also indicate at least one of the following: the multiplexing type of the frequency domain resource, the transmission direction of the frequency domain resource, or the maximum transmission power of the frequency domain resource.

[0243] In some example embodiments, frequency domain resources may be component carriers (CC), or frequency bands, or CCs with a single direction, or frequency bands with a single direction, and time domain resources may include at least one time slot, or at least one subframe, or at least one symbol.

[0244] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0245] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0246] In some example embodiments, a second means capable of performing any of the methods 600 (e.g., Figure 1 The second device 120 may include a component for performing the corresponding operation of method 600. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.

[0247] In some example embodiments, the second device may include: a component for sending configuration information to the first device, the configuration information indicating a resource aggregation pattern associated with a set of frequency domain resources, the resource aggregation pattern including at least one sub-pattern, different sub-patterns corresponding to different subsets of the set of frequency domain resources and different time domain resources; and a component for performing communication with the first device based on the configuration information.

[0248] In some example embodiments, the second device may further include: a component for receiving capability-related information from the first device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with resource aggregation patterns supported by the first device; and a component for determining configuration information based at least in part on the capability-related information.

[0249] In some example embodiments, the maximum number of frequency domain resources associated with the resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with the resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with the resource aggregation pattern supported by the first device, and a third maximum number of downlink frequency domain resources associated with the resource aggregation pattern supported by the first device.

[0250] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0251] In some example embodiments, the resource aggregation pattern may satisfy at least one of the following: requirements for capability-related information, requirements for a set of predefined switching rules, or requirements for maximum sensitivity degradation (MSD).

[0252] In some example embodiments, the second apparatus may further include: a component for determining a set of frequency domain resources associated with the resource aggregation pattern, wherein the number of frequency domain resources included in the set of frequency domain resources is less than or equal to a first maximum number and is permitted to be greater than the maximum number of frequency domain resources simultaneously active supported at the first apparatus, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than or equal to a second maximum number and is permitted to be greater than the maximum number of uplink frequency domain resources simultaneously active supported at the first apparatus, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than or equal to a third maximum number and is permitted to be greater than the maximum number of downlink frequency domain resources simultaneously active supported at the first apparatus.

[0253] In some example embodiments, the configuration information may indicate at least one of the following: at least one uplink frequency domain resource included in a set of frequency domain resources, at least one downlink frequency domain resource included in a set of frequency domain resources, at least one subpattern, a switching condition between at least one different subpattern, at least one subset of a set of frequency domain resources corresponding to at least one subpattern, or at least one verification time window corresponding to at least one subpattern.

[0254] In some example embodiments, the first message may include information about at least one uplink frequency domain resource and at least one downlink frequency domain resource, and the second message may include information about at least one of the following: at least one subpattern, at least one switching condition, at least one subset of a set of frequency domain resources, or at least one verification time window.

[0255] In some example embodiments, the configuration information may include an indication that instructs the first device to activate all frequency domain resources included in a set of frequency domain resources.

[0256] In some example embodiments, the second apparatus may further include: a component for sending a message to the first apparatus based on determining that at least one update condition is met, the message being used to update a resource aggregation pattern, wherein the message is used for at least one of the following: incorporating at least one new frequency domain resource into a group of frequency domain resources, excluding at least one frequency domain resource from the group of frequency domain resources, or invalidating at least one time-frequency resource of the resource aggregation pattern.

[0257] In some example embodiments, at least one update condition may be associated with at least one of the following: the inference state at the first device, the power margin state of the first device, or the maximum sensitivity degradation (MSD) state at the first device.

[0258] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0259] In some example embodiments, the second device may further include a component for receiving a message from the first device, the message indicating at least one of the following: the resource aggregation pattern is updated by the first device by invalidating at least one time-frequency resource of the resource aggregation pattern, an updated resource aggregation pattern, or a reason for updating.

[0260] In some example embodiments, for each frequency domain resource, the configuration information may also indicate at least one of the following: the multiplexing type of the frequency domain resource, the transmission direction of the frequency domain resource, or the maximum transmission power of the frequency domain resource.

[0261] In some example embodiments, frequency domain resources may be component carriers (CC), or frequency bands, or CCs with a single direction, or frequency bands with a single direction, and time domain resources may include at least one time slot, or at least one subframe, or at least one symbol.

[0262] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0263] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0264] In some example embodiments, a first means capable of performing any of the methods 700 (e.g., Figure 1 The first device 110 may include a component for performing the corresponding operation of method 700. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0265] In some example embodiments, the first device may include components for receiving configuration information from the second device, the configuration information indicating a plurality of resource aggregation patterns; and components for determining a resource aggregation pattern from the plurality of resource aggregation patterns based on at least one of the following: at least one condition for applying a resource aggregation pattern from the plurality of resource aggregation patterns, or an indication from the second device indicating a resource aggregation pattern to be applied from the plurality of resource aggregation patterns, wherein each resource aggregation pattern is associated with a set of frequency domain resources, and wherein the number of frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of frequency domain resources simultaneously active supported at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of uplink frequency domain resources simultaneously active supported at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of downlink frequency domain resources simultaneously active supported at the first device.

[0266] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0267] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0268] In some example embodiments, the first device may further include: a component for sending an indication that the first condition has been met to the second device in response to the first condition corresponding to the first resource aggregation pattern being met; and a component for receiving a message from the second device that instructs the first device to switch to applying the first resource aggregation pattern.

[0269] In some example embodiments, the first device may further include: a component for switching to apply the first resource aggregation pattern in response to the satisfaction of a first condition corresponding to the first resource aggregation pattern; and a component for sending a message to the second device, the message indicating at least one of the following: the first device has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern.

[0270] In some example embodiments, the first device may further include a component for sending capability-related information to the second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with resource aggregation patterns supported by the first device.

[0271] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0272] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, or the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0273] In some example embodiments, the frequency domain resource may be a component carrier (CC), or a frequency band, or a CC with a single direction, or a frequency band with a single direction.

[0274] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0275] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0276] In some example embodiments, a second means capable of performing any of the methods 800 (e.g., Figure 1 The second device 120 may include a component for performing the corresponding operation of method 800. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.

[0277] In some example embodiments, the second device may include components for sending configuration information to the first device, the configuration information indicating a plurality of resource aggregation patterns; and components for sending at least one of the following to the first device: at least one condition for applying a resource aggregation pattern from the plurality of resource aggregation patterns, or an indication from the second device indicating a resource aggregation pattern to be applied from the plurality of resource aggregation patterns, wherein each resource aggregation pattern is associated with a set of frequency domain resources, and wherein the number of frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of frequency domain resources simultaneously active supported at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of uplink frequency domain resources simultaneously active supported at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is allowed to be greater than the maximum number of downlink frequency domain resources simultaneously active supported at the first device.

[0278] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0279] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0280] In some example embodiments, the second device may further include: a component for receiving from the first device an indication that a first condition corresponding to a first resource aggregation pattern has been met; and a component for sending a message to the first device, the message instructing the first device to switch to applying the first resource aggregation pattern.

[0281] In some example embodiments, the second device may further include a component for sending a message to the first device in response to the satisfaction of a first condition corresponding to the first resource aggregation pattern, the message instructing the first device to switch to applying the first resource aggregation pattern.

[0282] In some example embodiments, the second device may further include: a component for receiving capability-related information from the first device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with resource aggregation patterns supported by the first device; and a component for determining configuration information based at least in part on the capability-related information.

[0283] In some example embodiments, the frequency domain resource may be a component carrier (CC), or a frequency band, or a CC with a single direction, or a frequency band with a single direction.

[0284] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0285] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0286] In some example embodiments, a first means capable of performing any of the methods 900 (e.g., Figure 1 The first device 110 may include a component for performing the corresponding operation of method 900. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.

[0287] In some example embodiments, the first device may include: a unit for sending capability-related information to the second device, the capability-related information indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; and a component for receiving configuration information from the second device, the configuration information indicating at least one resource aggregation pattern determined by the second device at least in part based on the capability-related information.

[0288] In some example embodiments, a resource aggregation pattern may be associated with a set of frequency domain resources, and wherein the resource aggregation pattern includes at least one sub-pattern, and different sub-patterns correspond to different subsets of the set of frequency domain resources and different time domain resources.

[0289] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0290] In some example embodiments, a resource aggregation pattern may be associated with a set of frequency domain resources, wherein the number of frequency domain resources included in the set of frequency domain resources is less than a first maximum number and is allowed to be greater than or equal to the maximum number of frequency domain resources simultaneously active at the first device, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than a second maximum number and is allowed to be greater than or equal to the maximum number of uplink frequency domain resources simultaneously active at the first device, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than a third maximum number and is allowed to be greater than or equal to the maximum number of downlink frequency domain resources simultaneously active at the first device.

[0291] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, and the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0292] In some example embodiments, at least one resource aggregation pattern may include a first resource aggregation pattern associated with a first group of frequency domain resources, and the configuration information may indicate at least one of the following: at least one uplink frequency domain resource included in the first group of frequency domain resources, at least one downlink frequency domain resource included in the first group of frequency domain resources, at least one first sub-pattern included in the first resource aggregation pattern, a switching condition between at least one different first sub-pattern, at least one first subset of the first group of frequency domain resources corresponding to at least one first sub-pattern, or at least one first time domain resource corresponding to at least one first sub-pattern.

[0293] In some example embodiments, the first device may further include: a component for communicating with the second device using a first sub-pattern; and a component for switching the first sub-pattern to the second sub-pattern based on configuration information by at least one of the following: switching uplink frequency domain resources of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern, switching downlink frequency domain resources of the first sub-pattern to uplink frequency domain resources of the second sub-pattern, switching uplink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, or switching downlink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

[0294] In some example embodiments, the first device may further include: a component for determining a resource aggregation pattern from at least one resource aggregation pattern based on at least one of the following: at least one condition for applying a resource aggregation pattern from a plurality of resource aggregation patterns, or an indication from a second device that indicates the resource aggregation pattern to be applied from a plurality of resource aggregation patterns.

[0295] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0296] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0297] In some example embodiments, the first device may further include: a component for sending an indication that the first condition has been met to the second device in response to the first condition corresponding to the first resource aggregation pattern being met; and a component for receiving a message from the second device that instructs the first device to switch to applying the resource aggregation pattern.

[0298] In some example embodiments, the first device may further include: a component for switching to apply the first resource aggregation pattern in response to the satisfaction of a first condition corresponding to the first resource aggregation pattern; and a component for sending a message to the second device, the message indicating at least one of the following: the first device has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern.

[0299] In some example embodiments, the frequency domain resource may be a component carrier (CC), or a frequency band, or a CC with a single direction or a frequency band with a single direction.

[0300] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0301] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0302] In some example embodiments, a second means capable of performing any of the methods 1000 (e.g., Figure 1 The second device 120 may include a component for performing a corresponding operation of method 1000. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.

[0303] In some example embodiments, the second device may include: components for receiving capability-related information from the first device indicating at least one of the following: handover-related capabilities between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first device, or the maximum number of frequency domain resources associated with a resource aggregation pattern supported by the first device; components for determining at least one resource aggregation pattern based at least in part on capability-related information; and components for sending configuration information including at least one resource aggregation pattern to the first device.

[0304] In some example embodiments, the resource aggregation pattern may satisfy at least one of the following: requirements for capability-related information, requirements for a set of predefined switching rules, or requirements for maximum sensitivity degradation (MSD).

[0305] In some example embodiments, the maximum number of frequency domain resources associated with a resource aggregation pattern may include at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with a resource aggregation pattern supported by the first device, a second maximum number of uplink frequency domain resources associated with a resource aggregation pattern supported by the first device, or a third maximum number of downlink frequency domain resources associated with a resource aggregation pattern supported by the first device.

[0306] In some example embodiments, the handover-related capabilities may include at least one of the following: whether the first device supports switching from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to another uplink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first device to switch from a downlink frequency domain resource to an uplink frequency domain resource, whether the first device supports switching from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first device to switch from an uplink frequency domain resource to a downlink frequency domain resource, whether the first device supports switching from a downlink frequency domain resource to another downlink frequency domain resource, and the duration required for the first device to switch from a downlink frequency domain resource to another downlink frequency domain resource.

[0307] In some example embodiments, the second apparatus may further include: a component for determining a set of frequency domain resources associated with a resource aggregation pattern, wherein the number of frequency domain resources included in the set of frequency domain resources is less than or equal to a first maximum number and is permitted to be greater than the maximum number of frequency domain resources simultaneously activated and supported at the first apparatus, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than or equal to a second maximum number and is permitted to be greater than the maximum number of uplink frequency domain resources simultaneously activated and supported at the first apparatus, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than or equal to a third maximum number and is permitted to be greater than the maximum number of downlink frequency domain resources simultaneously activated and supported at the first apparatus.

[0308] In some example embodiments, a resource aggregation pattern may be associated with a set of frequency domain resources, and wherein the resource aggregation pattern includes at least one sub-pattern, and different sub-patterns correspond to different subsets of the set of frequency domain resources and different time domain resources.

[0309] In some example embodiments, at least one resource aggregation pattern may include a first resource aggregation pattern associated with a first group of frequency domain resources, and the configuration information may indicate at least one of the following: at least one uplink frequency domain resource included in the first group of frequency domain resources, at least one downlink frequency domain resource included in the first group of frequency domain resources, at least one first sub-pattern included in the first resource aggregation pattern, a switching condition between at least one different first sub-pattern, at least one first subset of the first group of frequency domain resources corresponding to at least one first sub-pattern, or at least one first time domain resource corresponding to at least one first sub-pattern.

[0310] In some example embodiments, the first device may support switching between different resource aggregation patterns, and the first device may support being configured with more than one resource aggregation pattern, and the first device may also be configured to send at least one of the following to the first device: at least one condition for applying a resource aggregation pattern among the multiple resource aggregation patterns, or an indication from the second device indicating the resource aggregation pattern to be applied from the multiple resource aggregation patterns.

[0311] In some example embodiments, at least one condition may be associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0312] In some example embodiments, the MSD state may be associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0313] In some example embodiments, the second device may further include: a component for receiving from the first device an indication that a first condition corresponding to a first resource aggregation pattern has been met; and a component for sending a message to the first device, the message instructing the first device to switch to applying the first resource aggregation pattern.

[0314] In some example embodiments, the second device may further include a component for sending a message to the first device in response to a first condition corresponding to the first resource aggregation pattern being met, the message instructing the first device to switch to applying the first resource aggregation pattern.

[0315] In some example implementations, configuration information may be included in Radio Resource Control (RRC) signaling.

[0316] In some example embodiments, the first device may include a terminal device, and the second device may include a network device.

[0317] Figure 11 This is a simplified block diagram of a device 1100 suitable for implementing exemplary embodiments of the present disclosure. The device 1100 can be provided to implement a communication device, such as... Figure 1 The first device 110 or the second device 120 shown. As shown, device 1100 includes one or more processors 1110, one or more memories 1120 coupled to processor 1110, and one or more communication modules 1140 coupled to processor 1110.

[0318] Communication module 1140 is used for bidirectional communication. Communication module 1140 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1140 may include at least one antenna.

[0319] As a non-limiting example, processor 1110 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1100 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0320] Memory 1120 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1124, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1122 and other volatile memories that will not persist for the duration of a power outage.

[0321] Computer program 1130 includes computer-executable instructions that are executed by an associated processor 1110. The instructions of program 1130 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1130 may be stored in memory (e.g., ROM 1124). Processor 1110 can perform any suitable actions and processes by loading program 1130 into RAM 1122.

[0322] Example embodiments of this disclosure can be implemented by program 1130, enabling device 1100 to execute as described in the reference. Figures 5 to 10 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0323] In some example embodiments, program 1130 may be tangibly contained in a computer-readable medium, which may be included in device 1100 (such as memory 1120) or other storage device accessible by device 1100. Device 1100 may load program 1130 from the computer-readable medium into RAM 1122 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0324] Figure 12 An example of a computer-readable medium 1200 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1200 has a program 1130 stored thereon.

[0325] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0326] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0327] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0328] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0329] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0330] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless expressly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless expressly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0331] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0332] Clause 1. A first means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first means to: send capability-related information to a second means, the capability-related information indicating at least one of the following: handover-related capability between different frequency domain resources, whether the first means supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first means, or the maximum number of frequency domain resources associated with the resource aggregation patterns supported by the first means; and receive configuration information from the second means indicating at least one resource aggregation pattern, the at least one resource aggregation pattern being determined by the second means at least in part based on the capability-related information.

[0333] Clause 2. The first apparatus according to Clause 1, wherein the resource aggregation pattern is associated with a set of frequency domain resources, and wherein the resource aggregation pattern includes at least one sub-pattern, and different sub-patterns correspond to different subsets of the set of frequency domain resources and different time domain resources.

[0334] Clause 3. The first apparatus according to Clause 1, wherein the maximum number of frequency domain resources associated with the resource aggregation pattern includes at least one of the following: a first maximum number of uplink and downlink frequency domain resources associated with the resource aggregation pattern supported by the first apparatus, a second maximum number of uplink frequency domain resources associated with the resource aggregation pattern supported by the first apparatus, or a third maximum number of downlink frequency domain resources associated with the resource aggregation pattern supported by the first apparatus.

[0335] Clause 4. The first apparatus according to Clause 3, wherein the resource aggregation pattern is associated with a set of frequency domain resources, and wherein the number of frequency domain resources included in the set of frequency domain resources is less than the first maximum number and is allowed to be greater than or equal to the maximum number of frequency domain resources simultaneously active at the first apparatus, and / or the number of uplink frequency domain resources included in the set of frequency domain resources is less than the second maximum number and is allowed to be greater than or equal to the maximum number of uplink frequency domain resources simultaneously active at the first apparatus, and / or the number of downlink frequency domain resources included in the set of frequency domain resources is less than the third maximum number and is allowed to be greater than or equal to the maximum number of downlink frequency domain resources simultaneously active at the first apparatus.

[0336] Clause 5. The first apparatus according to Clause 1, wherein the handover-related capability includes at least one of the following: whether the first apparatus supports handover from an uplink frequency domain resource to another uplink frequency domain resource, the duration required for the first apparatus to handover from an uplink frequency domain resource to another uplink frequency domain resource, whether the first apparatus supports handover from a downlink frequency domain resource to an uplink frequency domain resource, the duration required for the first apparatus to handover from a downlink frequency domain resource to an uplink frequency domain resource, whether the first apparatus supports handover from an uplink frequency domain resource to a downlink frequency domain resource, the duration required for the first apparatus to handover from an uplink frequency domain resource to a downlink frequency domain resource, whether the first apparatus supports handover from a downlink frequency domain resource to another downlink frequency domain resource, and the duration required for the first apparatus to handover from a downlink frequency domain resource to another downlink frequency domain resource.

[0337] Clause 6. The first apparatus according to Clause 1, wherein the at least one resource aggregation pattern includes a first resource aggregation pattern associated with a first group of frequency domain resources, and the configuration information indicates at least one of the following: at least one uplink frequency domain resource included in the first group of frequency domain resources, at least one downlink frequency domain resource included in the first group of frequency domain resources, at least one first sub-pattern included in the first resource aggregation pattern, at least one switching condition between different first sub-patterns, at least one first subset of the first group of frequency domain resources corresponding to the at least one first sub-pattern, or at least one first time domain resource corresponding to the at least one first sub-pattern.

[0338] Clause 7. The first apparatus according to Clause 1, wherein the at least one resource aggregation pattern includes a first resource aggregation pattern, the first resource aggregation pattern includes a first sub-pattern and a second sub-pattern, and the first apparatus is further configured to: communicate with the second apparatus using the first sub-pattern; and, based on the configuration information, switch the first sub-pattern to the second sub-pattern by at least one of the following: switching an uplink frequency domain resource of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern, switching a downlink frequency domain resource of the first sub-pattern to an uplink frequency domain resource of the second sub-pattern, switching an uplink frequency domain resource of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, or switching a downlink frequency domain resource of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

[0339] Clause 8. The first apparatus according to Clause 1, wherein the first apparatus supports switching between different resource aggregation patterns and / or the first apparatus supports being configured with more than one resource aggregation pattern, and the first apparatus is further configured to: determine a resource aggregation pattern from the at least one resource aggregation pattern based on at least one of the following: at least one condition for applying the resource aggregation pattern among the plurality of resource aggregation patterns, or an indication from the second apparatus that indicates the resource aggregation pattern to be applied from the plurality of resource aggregation patterns.

[0340] Clause 9. The first device according to Clause 8, wherein the at least one condition is associated with at least one of the following: verification duration, inference state at the first device, power margin state of the first device, or maximum sensitivity degradation (MSD) state at the first device.

[0341] Clause 10. The first device according to Clause 9, wherein the MSD state is associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

[0342] Clause 11. The first device according to Clause 8, wherein the first device is further configured to: send an indication to the second device that the first condition is satisfied in response to the satisfaction of a first condition corresponding to a first resource aggregation pattern; and receive a message from the second device that instructs the first device to switch to applying the resource aggregation pattern.

[0343] Clause 12. The first device according to Clause 8, wherein the first device is further configured to: switch to apply the first resource aggregation pattern in response to the satisfaction of a first condition corresponding to the first resource aggregation pattern; and send a message to the second device indicating at least one of the following: the first device has switched to the first resource aggregation pattern, or a reason for switching to the first resource aggregation pattern.

[0344] Clause 13. A second means for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second means to: receive capability-related information from a first means, the capability-related information indicating at least one of the following: handover-related capability between different frequency domain resources, whether the first means supports handover between different resource aggregation patterns, the maximum number of configured resource aggregation patterns supported by the first means, or the maximum number of frequency domain resources associated with the resource aggregation patterns supported by the first means; determine at least one resource aggregation pattern based at least in part on the capability-related information; and send configuration information including the at least one resource aggregation pattern to the first means.

[0345] Clause 14. A method for communication, comprising: sending capability-related information to a second device, the capability-related information indicating at least one of the following: handover-related capability between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, a maximum number of configured resource aggregation patterns supported by the first device, or a maximum number of frequency domain resources associated with the resource aggregation pattern supported by the first device; and receiving from the second device configuration information indicating at least one resource aggregation pattern, the at least one resource aggregation pattern being determined by the second device at least in part based on the capability-related information.

[0346] Clause 15. A method for communication, comprising: receiving capability-related information from a first device, the capability-related information indicating at least one of the following: handover-related capability between different frequency domain resources, whether the first device supports handover between different resource aggregation patterns, a maximum number of configured resource aggregation patterns supported by the first device, or a maximum number of frequency domain resources associated with the resource aggregation pattern supported by the first device; determining at least one resource aggregation pattern based at least in part on the capability-related information; and sending configuration information including the at least one resource aggregation pattern to the first device.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to: Send capability-related information to the second device, the capability-related information indicating at least one of the following: The ability to switch between resources in different frequency domains Does the first device support switching between different resource aggregation patterns? The maximum number of resource aggregation patterns supported by the first device, or The maximum number of frequency domain resources associated with the resource aggregation pattern supported by the first device; and The second device receives configuration information indicating at least one resource aggregation pattern, which is determined by the second device based at least in part on the capability-related information.

2. The first apparatus of claim 1, wherein the resource aggregation pattern is associated with a set of frequency domain resources, and wherein the resource aggregation pattern includes at least one sub-pattern, and different sub-patterns correspond to different subsets of the set of frequency domain resources and different time domain resources.

3. The first apparatus of claim 1, wherein the maximum number of frequency domain resources associated with the resource aggregation pattern includes at least one of the following: The first maximum number of uplink and downlink frequency domain resources associated with the resource aggregation pattern supported by the first device. The second maximum number of uplink frequency domain resources associated with the resource aggregation pattern supported by the first device, or The third maximum number of downlink frequency domain resources associated with the resource aggregation pattern supported by the first device.

4. The first apparatus of claim 3, wherein the resource aggregation pattern is associated with a set of frequency domain resources, and wherein, The number of frequency domain resources included in the set of frequency domain resources is less than the first maximum number, and is allowed to be greater than or equal to the maximum number of frequency domain resources simultaneously active at the first device, and / or The number of uplink frequency domain resources included in the set of frequency domain resources is less than the second maximum number, and is allowed to be greater than or equal to the maximum number of uplink frequency domain resources simultaneously active at the first device, and / or The number of downlink frequency domain resources included in the set of frequency domain resources is less than the third maximum number, and is allowed to be greater than or equal to the maximum number of downlink frequency domain resources simultaneously activated at the first device.

5. The first apparatus according to claim 1, wherein the switching-related capability includes at least one of the following: Does the first device support switching from one uplink frequency domain resource to another? The duration required for the first device to switch from one uplink frequency domain resource to another. Does the first device support switching from downlink frequency domain resources to uplink frequency domain resources? The duration required for the first device to switch from downlink frequency domain resources to uplink frequency domain resources. Does the first device support switching from uplink frequency domain resources to downlink frequency domain resources? The duration required for the first device to switch from uplink frequency domain resources to downlink frequency domain resources. Does the first device support switching from one downlink frequency domain resource to another? The duration required for the first device to switch from one downlink frequency domain resource to another.

6. The first apparatus of claim 1, wherein the at least one resource aggregation pattern comprises a first resource aggregation pattern associated with a first set of frequency domain resources, and the configuration information indicates at least one of the following: At least one uplink frequency domain resource included in the first group of frequency domain resources At least one downlink frequency domain resource included in the first group of frequency domain resources At least one first sub-pattern included in the first resource aggregation pattern At least one switching condition between different first sub-patterns. At least one first subset of the first set of frequency domain resources corresponding to the at least one first sub-pattern, or At least one first time-domain resource corresponding to the at least one first sub-pattern.

7. The first apparatus of claim 1, wherein the at least one resource aggregation pattern comprises a first resource aggregation pattern, the first resource aggregation pattern comprising a first sub-pattern and a second sub-pattern, and the first apparatus is further configured such that: Using the first sub-pattern to communicate with the second device; and Based on the configuration information, the first sub-pattern is switched to the second sub-pattern by at least one of the following: Switch the uplink frequency domain resources of the first sub-pattern to another uplink frequency domain resource of the second sub-pattern. Switch the downlink frequency domain resources of the first sub-pattern to the uplink frequency domain resources of the second sub-pattern. Switch the uplink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern, or Switch the downlink frequency domain resources of the first sub-pattern to another downlink frequency domain resource of the second sub-pattern.

8. The first apparatus of claim 1, wherein the first apparatus supports switching between different resource aggregation patterns and / or the first apparatus supports being configured with more than one resource aggregation pattern, and the first apparatus is further configured such that: A resource aggregation pattern is determined from the at least one resource aggregation pattern based on at least one of the following: At least one condition for applying the resource aggregation pattern among the plurality of resource aggregation patterns, or Instructions from the second device indicate the resource aggregation pattern to be applied from the plurality of resource aggregation patterns.

9. The first apparatus of claim 8, wherein the at least one condition is associated with at least one of the following: Verification duration, The reasoning state at the first device. The power margin status of the first device, or The maximum sensitivity degradation (MSD) state at the first device.

10. The first apparatus of claim 9, wherein the MSD state is associated with at least one of the following: uplink harmonics, harmonic mixing, crossband isolation, and intermodulation.

Images