Method and system for utilizing carrier aggregation capabilities
By configuring user equipment using the network based on the UE's capability statement and configuration strategy in a 5G network, the problem of how to effectively utilize its additional capabilities when the UE is configured to process fewer component carriers than it can handle, and the communication performance is improved and the effect of resource utilization.
Patent Information
- Application Number
- CN202010674003.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-06-18
- Filing Date
- 2020-07-14
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-07-14
AI Technical Summary
In a 5G network, a user equipment (UE) is configured to effectively utilize the additional capabilities it can use to improve communication performance when it is configured to process fewer component carriers than it can handle.
The network receives the capability declaration of the UE and configures the first component carrier (CC) according to a configuration exceeding the first capability, for example, configuring the first CC to support multiple capabilities, such as overlapping physical downlink shared channels, disordered hybridization Automatically retransmit requests, etc., or use the combined capabilities of the first CC and the second CC to configure a more efficient CC.
In this way, the UE can provide additional functions in the configured CC, improve communication performance, free up resources to support more efficient processing and storage capabilities, and enhance network performance.
Smart Images

Figure CN112242895B_ABST
Abstract
Description
[0001] This application claims priority to and the benefit of U.S. Provisional Application No. 62 / 875,750, filed on July 18, 2019, entitled “System and Method for Processing Out-of-Order Hybrid Automatic Repeat Request (HARQ) with Hybrid Processing Time,” U.S. Provisional Application No. 62 / 970,636, filed on February 5, 2020, entitled “System and Method for Providing Capability Signaling for User Equipment (UE) Supporting Multiple Transmission and Reception Points (M-TRP),” and U.S. Non-Provisional Application No. 16 / 905,673, filed on June 18, 2020, entitled “System and Method for Using Carrier Aggregation Capabilities,” the entire contents of which are incorporated herein by reference. Technical Field
[0002] One or more aspects according to embodiments of the present disclosure relate to wireless communications, and more particularly, to a system and method for using excess capabilities available in a UE when the UE is configured for fewer component carriers than it can handle. Background Art
[0003] In a 5G network, a user equipment (UE) may declare various capabilities to the network, including, for example, the capability to support carrier aggregation (CA) with two or more component carriers (CCs), and the capability to support various functions for CCs (e.g., Capability 1 or Capability 2) for each component carrier. In some cases, the network may configure the UE with fewer CCs than the capabilities declared supported by the UE, and in this case, it may be beneficial for the network and the UE to utilize the excess UE capabilities that may be generated.
[0004] Therefore, there is a need for a system and method for utilizing the additional capabilities available in a UE. Summary of the invention
[0005] According to an embodiment of the present invention, a method is provided, comprising: receiving a capability declaration from a user equipment (UE) by a network, the capability declaration comprising: a first capability declaration for a first component carrier (CC) and a second capability declaration for a second CC; and configuring, by the network, one or more CCs for the UE including the first CC but not including the second CC, the configuration step comprising: configuring the first CC with a configuration exceeding the first capability.
[0006] In some embodiments: the first capability is Capability 1, the second capability is Capability 2, and the configuring step includes configuring the first CC to support both Capability 1 and Capability 2.
[0007] In some embodiments, the configuring step also includes: configuring the first CC to support a capability selected from the group consisting of: overlapping physical downlink shared channel (PDSCH), overlapping physical uplink shared channel (PUSCH), out-of-order PDSCH, out-of-order PUSCH, and out-of-order hybrid automatic repeat request (HARQ).
[0008] In some embodiments: the first capability is Capability 2, the second capability is Capability 2, and the configuring step includes: configuring the first CC to support out-of-order hybrid automatic repeat request (HARQ) between overlapping Capability 2 physical downlink shared channels (PDSCHs).
[0009] In some embodiments: the first capability is single transmit and receive point (TRP) operation, the second capability is single transmit and receive point (TRP) operation, and the configuring step includes configuring the first CC to support multiple transmit and receive point (M-TRP) operation.
[0010] In some embodiments: the first capability is time slot based physical downlink control channel (PDCCH) monitoring, the second capability is span based PDCCH monitoring, and the configuration step includes: configuring the first CC to monitor PDCCH candidates using both time slot based PDCCH monitoring and span based PDCCH monitoring.
[0011] In some embodiments: the first capability includes a first rank and a first modulation order; the second capability includes a second rank and a second modulation order; and the configuring step includes configuring the first CC using the lower of the first rank and the second rank and the lower of the first modulation order and the second modulation order.
[0012] In some embodiments: the first capability includes a first rank and a first modulation order; the second capability includes a second rank and a second modulation order; and the configuration step includes: configuring the first CC to receive a first physical downlink shared channel (PDSCH) using the first capability and a second physical downlink shared channel (PDSCH) using the second capability.
[0013] In some embodiments: the declaration of the capability includes declaring one of two capabilities for each of N CCs including a first CC and a second CC, wherein N is an integer greater than 2, and the step of declaring one of the two capabilities for each of N CCs including the first CC and the second CC includes: declaring a first capability for a first subset of the N CCs and declaring a second capability for a second subset of the N CCs; and the step of configuring includes: configuring k CCs of the N CCs for the UE by the network, wherein k is a positive integer, and configuring p CCs of the k CCs by the network using a configuration that exceeds both the first capability and the second capability, wherein p is equal to the smaller of k and Nk.
[0014] According to an embodiment of the present invention, a method is provided, comprising: sending a capability declaration by a user equipment UE to a network, the capability declaration comprising a first capability declaration for a first component carrier (CC) and a second capability declaration for a second CC; and configuring, by the UE in response to a configuration command received from the network, one or more CCs including the first CC but not including the second CC, the configuration step comprising: configuring the first CC with a configuration exceeding the first capability.
[0015] In some embodiments: the first capability is Capability 1, the second capability is Capability 2, and the step of configuring includes configuring the first CC to support both Capability 1 and Capability 2.
[0016] In some embodiments, the configuring step also includes: configuring the first CC to support a capability selected from the group consisting of: overlapping physical downlink shared channel (PDSCH), overlapping physical uplink shared channel (PUSCH), out-of-order PDSCH, out-of-order PUSCH, and out-of-order hybrid automatic repeat request (HARQ).
[0017] In some embodiments: the first capability is Capability 2, the second capability is Capability 2, and the configuring step includes: configuring the first CC to support out-of-order hybrid automatic repeat request (HARQ) between overlapping Capability 2 physical downlink shared channels (PDSCHs).
[0018] In some embodiments: the first capability is single transmit and receive point (TRP) operation, the second capability is single transmit and receive point (TRP) operation, and the configuring step includes configuring the first CC to support multiple transmit and receive point (M-TRP) operation.
[0019] In some embodiments: the first capability is time slot-based physical downlink control channel (PDCCH) monitoring, and the second capability is span-based PDCCH monitoring, and the configuration step includes configuring the first CC to monitor PDCCH candidates using both time slot-based PDCCH monitoring and span-based PDCCH monitoring.
[0020] In some embodiments: the first capability includes a first rank and a first modulation order; the second capability includes a second rank and a second modulation order; and the configuring step includes configuring the first CC using the lower of the first rank and the second rank and the lower of the first modulation order and the second modulation order.
[0021] In some embodiments: the first capability includes a first rank and a first modulation order; the second capability includes a second rank and a second modulation order; and the configuration step includes: configuring the first CC to receive a first physical downlink shared channel (PDSCH) using the first capability and a second physical downlink shared channel (PDSCH) using the second capability.
[0022] In some embodiments: the declaration of the capability includes declaring one of the two capabilities for each of N CCs including a first CC and a second CC, wherein N is an integer greater than 2, and the step of declaring one of the two capabilities for each of N CCs including the first CC and the second CC includes: declaring a first capability for a first subset of the N CCs and declaring a second capability for a second subset of the N CCs; and the step of configuring one or more CCs including the first CC but not including the second CC includes: configuring k CCs out of the N CCs by the UE, wherein k is a positive integer; configuring p CCs out of the k CCs by the UE using a configuration exceeding both the first capability and the second capability, wherein p is equal to the smaller of k and Nk.
[0023] In some embodiments, k is less than one-half of N.
[0024] According to an embodiment of the present invention, a method is provided, comprising: a network sending a first physical downlink shared channel (PDSCH) to a user equipment (UE) at a first time point, wherein the first PDSCH is a Capability 1 PDSCH; the network sending a Capability 2 physical downlink shared channel (PDSCH) to the user equipment (UE); the network receiving a physical uplink control channel (PUCCH) corresponding to the first PDSCH from the UE at a second time point, wherein the second time point is later than the first time point by an amount exceeding the normal maximum response delay specified by the standard for Capability 1 PDSCH. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] These and other features and advantages of the present disclosure will be appreciated and understood with reference to the specification, claims and drawings, in which:
[0026] Figure 1 is a block diagram according to an embodiment of the present disclosure;
[0027] Figure 2 is a flow chart according to an embodiment of the present disclosure; and
[0028] Figure 3 is a schematic timing diagram according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0029] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of an exemplary embodiment of a system and method for using additional capabilities available in a UE when the UE is configured for fewer component carriers than it can handle according to the present disclosure, and is not intended to represent the only form in which the present disclosure can be constructed or utilized. This specification sets forth the features of the present disclosure in conjunction with the illustrated embodiments. However, it should be understood that the same or equivalent functions and structures may be implemented by different embodiments that are also intended to be included within the scope of the present disclosure. As indicated elsewhere herein, the same element numbers are intended to indicate the same elements or features.
[0030] Figure 1 is a simplified block diagram of two components of a 5G communication system in some embodiments. A user equipment (UE) 105 forms a connection (e.g., a wireless connection) with a network 110 (e.g., with a base station of the network 110). In a 5G communication system, when carrier aggregation (CA) is adopted, the user equipment (UE) 105 may declare to the network 110 how many component carriers (CCs) it can support, and the UE 105 may also declare to the network 110 what capabilities it has for each CC. In some embodiments, if the network 110 subsequently configures the UE 105 with fewer CCs than the number declared by the UE, the UE may be able to provide additional capabilities for the CCs configured for it. As used herein, certain phrases such as "user equipment" and "downlink control information" (discussed in further detail below) expressed in the singular may also be used to refer to the plural form.
[0031] As described above, in one aspect of signaling capabilities by the UE to the network, the UE may declare its CA capability to indicate that it is able to support N CCs or "cells". However, in some cases, the network may subsequently configure the UE with fewer CCs than the value N declared by the UE. In such a case, which may be referred to as an "unused CA capability" case, the network may assume that some of the configured cells may be configured to support additional functionality (i.e., functionality in addition to those for which the UE has declared capabilities) via implicit indication. The reason for the ability to support additional functionality may be that relieving the UE of the need to process some of the CCs for which it has declared capabilities may free up resources in the UE (e.g., processing, memory, or power resources), which the UE may instead employ to provide additional functionality for some or all of the CCs configured for the UE.
[0032] In some embodiments, this may mean that the UE may have capabilities for parallel (or additional) processing by utilizing unused CA (carrier aggregation) capabilities. In this case, for example, the UE may declare a capability set (i.e., the UE may send a declaration of capabilities to the network, and the network may receive a declaration of capabilities from the UE), wherein the declaration of capabilities includes a declaration of a first capability (e.g., capabilities referred to herein as "Function 1") for a first component carrier (CC) and a declaration of a second capability (e.g., capabilities referred to herein as "Function 2") for a second CC. If only one CC is configured to the UE, the UE may also be able to support two functions combined in one CC (i.e., Function 1 and Function 2). More generally, if the network configures the UE with one or more CCs that include the first CC but do not include the second CC (i.e., the network configures the UE with fewer CCs than the UE declares that it can process), the network may configure the first CC with a configuration that exceeds the first capability (e.g., configuring the first CC to support both Function 1 and Function 2).
[0033] Figure 2A flow chart of this process is shown for the case involving two CCs. In a given band of a band combination (BoBC), at 205, the UE may declare: (i) the number of CCs for which the UE supports only low priority channels or low priority operations (e.g., Capability 1 channels) (e.g., 2 CCs), and (ii) the number of CCs that the UE supports when the UE is configured with both low priority channels or operations and high priority channels or operations (e.g., one CC at low priority and one CC at high priority). At 210, the network may then configure the UE with any of the following three possible configurations: (i) the network may configure a first CC (e.g., CC0) of the two CCs for low priority operation and the network may configure a second CC (e.g., CC1) of the two CCs for low priority operation, (ii) the network may configure the first CC (CC0) for low priority operation and the network may configure the second CC (CC1) for high priority operation, or (iii) the network may configure the first CC (CC0) for low priority operation and the network may configure the first CC (CC0) for high priority operation (i.e., in option (iii), the network may configure only the first CC with a configuration that exceeds the first capability).
[0034] Function 1 and Function 2 may include various capabilities that the UE may provide. As a first example, Function 1 may be support for Capability 1 and Function 2 may be support for Capability 2. In this example, the combined functionality may be support for hybrid capabilities for a single cell (i.e., for a single CC), wherein the hybrid capabilities include out-of-order (OoO) processing of overlapping physical downlink shared channels (PDSCHs) and transmission of OoO physical uplink shared channels (PUSCHs) or transmission of OoO hybrid automatic repeat request (HARQ). As used herein, the phrases "Capability 1" and "Capability 2" represent terms with these names defined in the 5G standard (e.g., in Release 16), and refer to basic processing speed and low-latency services, respectively. The word "capability" as used herein has its ordinary Chinese meaning and refers to any capability (e.g., of a UE).
[0035] As a second example, function 1 may be support for single transmit and receive point (TRP) operation (e.g., single CORESETPoolIndex), and function 2 may be the same as function 1. Like this, the UE may support single TRP operation for each CC when configured with only the declared capabilities. When the UE is configured with fewer CCs than the declared number, the combined functionality supported for one of the CCs may be support for two TRPs for the same CC (i.e., support for M-TRP functionality on that CC).
[0036] As a third example, function 1 may be slot-based PDCCH monitoring (as in Release 15), and function 2 may be span-based PDCCH monitoring (introduced in Release 16). In this example, the combined function may be hybrid PDCCH monitoring. That is, the UE may monitor certain PDCCH candidates based on slot-based monitoring restrictions, and monitor certain other candidates based on span-based monitoring restrictions.
[0037] If capability 1 is Capability 1 and capability 2 is Capability 2, further restrictions can be implemented. Call the Capability 1 restriction N 1 And the Capability 2 limit is called N 1 ', if two PDSCHs are sent to the UE so that an OoO situation is created, their Ack / Nack timing T 1 and T 1 '(T 1 and T 1 ' can be configured by the network to the UE) can fall into one of the following three situations:
[0038] 1)T 1 >N 1 >T 1 '>N 1 '
[0039] 2) T 1 >T 1 '>N 1 >N 1 '
[0040] 3)N 1 >T 1 >T 1 '>N 1 '
[0041] In case 1) and case 2), the UE may be expected to be able to process the combined functions in a CC configured to support the combination of Function 1 and Function 2, but in case 3), the UE may not be able to support the combination of Function 1 and Function 2 because doing so may require running two parallel Capability 2 processes. A candidate approach to this potential problem may be to configure the network so that it does not allow case 3) to occur, but this approach may be disadvantageous if the 5G standard evolves to cover case 3) in the future. In this case, restrictions on OoO combinations may be used, depending on the declared UE capabilities and unused CA capabilities. For example, the network may allow case 3) to occur only when two CCs with Capability 2 declarations are available for processing in one CC.
[0042] In the first example where function 1 is Capability 1 and function 2 is Capability 2, the UE declares dual CCCA (i.e., supports CA with two CCs), where one CC has the capability of Capability 1 and one CC has the capability of Capability 2. In this case, the network may decide to configure only one CC, and may send both Capability 1 PDSCH and Capability 2 PDSCH to the UE involving OoO HARQ between Capability 1 PDSCH and Capability 2 PDSCH. In this example, the network may not configure one CC for the UE, and send Capability 2 PDSCH involving OoO HARQ.
[0043] In the second example where function 1 is Capability 1 and function 2 is Capability 2, the UE declares dual CCCA, where both CCs have the capability of Capability 2. The network may decide to configure only one CC, and may send both Capability 1 PDSCH and Capability 2 PDSCH to the UE involving OoO HARQ between Capability 1 PDSCH and Capability 2 PDSCH. The network may also decide to configure only one CC, and may send Capability 2 PDSCH involving OoO HARQ.
[0044] In some cases, the UE's ability to support a combination of functions (such as Capability 1 and Capability 2) may be affected by the PHY parameters used. For example, in inter-band CA BC (band combination), the UE may have declared support for Function 1 with a rank of 4 and a modulation order of 256QAM in the first CC (CC0), and the UE may have declared support for Function 2 with a rank of 2 and a modulation order of 64QAM in the second CC (CC1). In this case, even if only CC0 is configured, it may not be realistic for the UE to process a combination of Function 1 and Function 2 with a rank of 4 and a maximum data rate corresponding to 256QAM.
[0045] This potential difficulty can be addressed in several ways, with two exemplary solutions given below. In the first exemplary solution, (i) the CC0 configuration is restricted for each PHY parameter to the minimum PHY parameter value among the values for CC0 and CC1 (i.e., the PHY parameter value that is the least burdensome), or (ii) the CC0 configuration is restricted to a combination of PHY parameters (a combination of CC0 (e.g., rank 4, 256QAM) and a combination of CC1 (e.g., rank 2, 64QAM)). In some embodiments, for a subset (e.g., rank, modulation order, or the entire set of parameters that the UE has declared), the minimum value between a CC that has declared function 1 and a CC that has declared function 2 may be used as a restriction on the corresponding PHY parameters for the CC supporting the combined function 1 and function 2.
[0046] In a first example using the first exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for Capability 1, rank 4, and 256QAM, and the other CC is configured for Capability 2, rank 2, and 64QAM. In this case, the network may decide to configure only one CC, and may send both Capability 1 PDSCH and Capability 2 PDSCH to the UE for OoO HARQ between Capability 1 PDSCH and Capability 2 PDSCH. PDSCH may have a maximum rank of 2 and a maximum data rate of up to 64QAM.
[0047] In a second example using the first exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for a single TRP, rank 4, and 256QAM, and the other CC is configured for a single TRP, rank 2, and 64QAM. In this case, the network may decide to configure only one CC, and may send PDSCH to the UE from both TRPs. The PDSCH may have a maximum rank of 2 and a maximum data rate of up to 64QAM.
[0048] In a third example using the first exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for slot-based PDCCH monitoring, rank 4, and 256QAM, and the other CC is configured for span-based PDCCH monitoring, rank 2, and 64QAM. In this case, the network may decide to configure only one CC with mixed slot-based and span-based PDCCH monitoring. The PDSCH may have a maximum rank of 2 and a maximum data rate of up to 64QAM.
[0049] In a second exemplary solution, for a subset (e.g., rank, modulation order, or the entire set of parameters that the UE has declared), when combined function 1 and function 2 are supported in one CC, the PHY parameter restrictions of the CC where the UE declared function 1 are applied to function 1 PDSCH, and the PHY parameter restrictions of the CC where the UE declared function 2 are applied to function 2 PDSCH. This exemplary solution can use the association of PDSCH with function to adopt the distinction of PDSCH according to function.
[0050] In a first example using this second exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for Capability 1, rank 4, and 256QAM, and the other CC is configured for Capability 2, rank 2, and 64QAM. In this case, the network may decide to configure only one CC, and may send both Capability 1 PDSCH and Capability 2 PDSCH to the UE involving OoO HARQ between Capability 1 PDSCH and Capability 2 PDSCH. Capability 1 PDSCH may have a maximum rank of 4 and a maximum data rate for 256QAM, and Capability 2 PDSCH may have a maximum rank of 2 and a maximum data rate for 64QAM.
[0051] In a second example using the second exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for a single TRP, rank 4, and 256QAM, and the other CC is configured for a single TRP, rank 2, and 64QAM. In this case, the network may decide to configure only one CC, and may send PDSCHs to the UE from both TRPs. The PDSCH associated with one of the two TRPs may have a rank of up to 4 and a maximum data rate of up to 256QAM. The PDSCH associated with the other TRP may have a rank of up to 2 and a maximum data rate of up to 64QAM.
[0052] In a third example using the second exemplary solution, the UE declares support for CA with two CCs, where one CC is configured for slot-based PDCCH monitoring, rank 4, and 256QAM, and the other CC is configured for span-based PDCCH monitoring, rank 2, and 64QAM. In this case, the network may decide to configure only one CC with mixed slot-based and span-based PDCCH monitoring. The PDSCH associated with slot-based PDCCH monitoring may have a maximum rank of 4 and a maximum data rate of up to 256QAM. The PDSCH associated with span-based PDCCH monitoring may have a maximum rank of 2 and a maximum data rate of up to 64QAM.
[0053] The concept of reusing unused CA capabilities can be applied in the context of intra-band CA. The above methods and examples can be generalized to the following case with CA including more than two CCs: If the UE declares N corresponding capabilities for N CCs, and the network decides to configure only k CCs (k is an integer less than N) for the UE, the UE can support the combined functionality for p CCs (p is min(k,Nk), i.e., p is equal to the smaller of k and Nk). For example, if the UE declares a CA capability of N=8 and the network configures k=5 cells for the UE, the UE and the network can assume that the UE supports the combined functionality for min(8-5,5)=3 cells (e.g., for the 3 cells with the lowest index or the highest index). As another example, if the UE declares a CA capability of N=6 and the network configures k=3 cells for the UE, the UE and the network can assume that the UE supports the combined functionality for min(6-3,3)=3 cells (e.g., for the 3 cells with the lowest index or the highest index, i.e., for all configured cells).
[0054] As used herein, "configuring" a UE means (i) configuring the UE itself in response to a configuration command received from the network, or (ii) sending a configuration command to the UE by the network. As such, the network may configure one or more CCs for the UE, where each CC has a configuration (which is typically one configuration for which the UE is capable), or equivalently, the UE may configure one or more CCs in response to a command from the network.
[0055] Figure 3 A method for accommodating UEs with limited processing capabilities is shown. In some of the examples discussed above, a UE that is not CA capable may not be able to support OoO HARQ. In some embodiments, this potential loss of capability for such UEs may be mitigated by appropriately increasing the Capability1 PDSCH processing time. Figure 3 A time sequence illustrating the operation of such a UE in the OoO HARQ case is shown.
[0056] like Figure 3 As shown in , the UE may stop processing of PDSCH1 and process PDSCH2 before resuming processing of PDSCH1. When processing of PDSCH1 is resumed, a UE with limited processing capabilities may not be able to meet the original PDSCH1 processing time (or "normal maximum response delay specified by the standard for Capability 1 PDSCH") due to the delay caused by processing PDSCH2. In order to complete the processing of PDSCH1 even with delays, in some embodiments, the PDSCH1 processing time requirement is relaxed (i.e., the allowable processing time is appropriately increased), and the network may receive the physical uplink control channel (PUCCH) corresponding to PDSCH1, even after a delay exceeding the normal maximum response delay specified by the standard for PDSCH of Capability 1. The amount of the increase may depend on the implementation; in some embodiments, the increase is equal to the timing parameter N for processing of Capability 2 PDSCH. 1 In some embodiments, the increase in allowable processing time is increased by adjusting Δ>=0 to account for UE burden.
[0057] For example, for a CC with Capability 2 enabled, the network may configure combined Capability 1 and Capability 2 processing with OoO HARQ. When combined Capability 1 and Capability 2 processing with OoO HARQ is configured, a network-allowed processing time for Capability 1 PDSCH is generated for Capability 1 PDSCH before Capability 2 PDSCH with OoO HARQ is generated, wherein the network-allowed processing time is increased by the processing time of Capability 2 PDSCH + Δ.
[0058] In some embodiments, the network ensures appropriate processing time when allocating its ACK / NACK (A / N) PUCCH. For example, the network may acknowledge this increased processing time when allocating A / N PUCCH for PDSCH1. However, when the network schedules PDSCH1 and its A / N resources, the network may not be aware of the existence of PDSCH2. In such a case, the signaled A / N resources for PDSCH1 may be implicitly delayed due to the increase in allowed processing time. When combined Capability 1 and Capability 2 processing with OoO HARQ is configured, the system may operate according to one of two methods.
[0059] In the first of these two methods, for Capability 1 PDSCH that precedes Capability 2 PDSCH that generates OoO HARQ, the UE may be configured to provide a valid HARQ-ACK message. If the allocated A / N PUCCH resources satisfy Capability 1, the PDSCH processing time may be increased by the network by the processing time of Capability 2 PDSCH + Δ. In the second of these two methods, for Capability 1 PDSCH that precedes Capability 2 PDSCH that generates OoO HARQ, the UE applies a delay amount of Capability 2 PDSCH processing time + Δ to the allocated A / NPUCCH resource timing. In this second method, a delay amount appropriately quantized to satisfy symbol boundary constraints and a priority rule for handling potential conflicts after applying the delay may be used.
[0060] In some embodiments, the network includes a first processing circuit (e.g., one or more CPUs), and the UE includes a processing circuit. The processing circuit may perform some or all of the methods described herein, for example, sending and receiving PDSCH and PUCCH (through suitable sending and receiving hardware (such as, radio, microwave or millimeter wave transmitters and receivers)), wherein some of the sending and receiving hardware may be outside the processing circuit. The term "processing circuit" is used herein to represent any combination of hardware, firmware and software for processing data or digital signals. The processing circuit hardware may include, for example, an application specific integrated circuit (ASIC), a general or dedicated central processing unit (CPU), a digital signal processor (DSP), a graphics processing unit (GPU) and a programmable logic device (such as, a field programmable gate array (FPGA)). In the processing circuit, as used herein, each function is performed by hardware configured (i.e., hardwired) to perform the function, or by more general hardware (e.g., CPU) configured to execute instructions stored in a non-temporary storage medium. The processing circuit may be manufactured on a single printed circuit board (PCB) or distributed on several interconnected PCBs. The processing circuit may include other processing circuits; for example, the processing circuit may include two processing circuits (FPGA and CPU) connected to each other on a PCB.
[0061] As used herein, "a portion" of something means "at least some" of that thing, and thus can mean less than all of that thing or all of that thing. Thus, "a portion" of a thing includes the entire thing as a special case, i.e., the entire thing is an example of a portion of a thing.
[0062] As used herein, the term "or" should be interpreted as "and / or", such that, for example, "A or B" means either "A" or "B" or "A and B". As used herein, when a method (e.g., adjustment) or a first quantity (e.g., a first variable) is referred to as being "based on" a second quantity (e.g., a second variable), it means that the second quantity is an input to the method or affects the first quantity, for example, the second quantity may be an input to a function that calculates the first quantity (e.g., the only input or one of several inputs), or the first quantity may be equal to the second quantity, or the first quantity may be the same as the second quantity (e.g., stored at the same location or multiple locations in memory).
[0063] It will be understood that although the terms "first", "second", "third", etc. may be used herein to describe various elements, components, regions, layers and / or parts, these elements, components, regions, layers and / or parts should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or part from another element, component, region, layer or part. Therefore, without departing from the spirit and scope of the present invention, the first element, component, region, layer or part discussed herein may be referred to as a second element, component, region, layer or part.
[0064] The term used herein is only used to describe the purpose of specific embodiment, and is not intended to limit the inventive concept. As used herein, the term "substantially", "about" and similar terms are used as approximate terms rather than degree terms, and are intended to explain the inherent deviation of the measured value or calculated value that those of ordinary skill in the art will recognize. As used herein, the term "main component" refers to the composition present in the composition, polymer or product in an amount larger than the amount of any other single component in the composition or product. On the contrary, the term "basic component" refers to the composition accounting for at least 50% weight or more of the composition, polymer or product. As used herein, the term "main part" represents at least half of the articles in the article when being applied to a plurality of articles.
[0065] As used herein, unless the context clearly indicates otherwise, the singular form is intended to also include the plural form. It will also be understood that when the term "include" and / or "contain" is used in this specification, the term "include" and / or "contain" specifies the existence of the stated features, integers, steps, operations, elements and / or components, but does not exclude the existence or addition of one or more other features, integers, steps, operations, elements, components and / or groups of features, integers, steps, operations, elements and components. As used herein, the term "and / or" includes any combination and all combinations of one or more of the associated listed items. Statements such as "at least one of ..." modify the entire element list when it is after the element list, without modifying the single element in the list. In addition, when describing the embodiment of the present invention, the use of "can" refers to "one or more embodiments of the present disclosure". In addition, the term "exemplary" is intended to refer to an example or explanation. As used herein, the terms "use", "being used" and "used" can be considered to be synonymous with the terms "utilize", "being utilized" and "utilized" respectively.
[0066] Any numerical range listed here is intended to include all subranges of the same numerical precision contained in the listed range. For example, the range of "1.0 to 10.0" or "between 1.0 and 10.0" is intended to include all subranges between the listed minimum value 1.0 and the listed maximum value 10.0 (and including the listed minimum value 1.0 and the listed maximum value 10.0), that is, the minimum value is equal to or greater than 1.0 and the maximum value is equal to or less than 10.0, such as, for example, 2.4 to 7.6. Any maximum numerical limit listed here is intended to include all lower numerical limits contained therein, and any minimum numerical limit listed in this specification is intended to include all higher numerical limits contained therein.
[0067] Although an exemplary embodiment of a system and method for using additional capabilities available in a UE when the UE is configured for fewer component carriers than it can handle has been specifically described and illustrated herein, many modifications and variations will be apparent to those skilled in the art. Therefore, it should be understood that the system and method for using additional capabilities available in a UE when the UE is configured for fewer component carriers than it can handle, constructed in accordance with the principles of the present disclosure, may be implemented differently than specifically described herein. The present invention is also defined in the appended claims and their equivalents.
Claims
1. A communication method, include: receiving, by the network, a declaration of capabilities from a user equipment UE, wherein the declaration of capabilities comprises a declaration of a first capability for a first component carrier CC and a declaration of a second capability for a second CC; and The network configures one or more CCs including the first CC but not including the second CC for the UE, The step of configuring includes: configuring the first CC with a configuration exceeding the first capability, Wherein, based on the first capability being Capability 1 and the second capability being Capability 2, the configuring step includes: configuring the first CC to support both Capability 1 and Capability 2.
2. The communication method according to claim 1, in, The configuring step further includes: configuring the first CC to support a capability selected from the group consisting of: overlapping physical downlink shared channel PDSCH, overlapping physical uplink shared channel PUSCH, out-of-order PDSCH, out-of-order PUSCH, and out-of-order hybrid automatic repeat request HARQ.
3. The communication method according to claim 1, in: Based on the first capability being Capability 2 and the second capability being Capability 2, the configuring step includes configuring the first CC to support out-of-order hybrid automatic repeat request HARQ between overlapping Capability 2 physical downlink shared channels PDSCH.
4. The communication method according to claim 1, in: Based on the first capability being single receiving and transmitting point TRP operation and the second capability being single receiving and transmitting point TRP operation, the configuration step includes configuring the first CC to support multiple receiving and transmitting point M-TRP operation.
5. The communication method according to claim 1, in: Based on the first capability being slot-based Physical Downlink Control Channel (PDCCH) monitoring and the second capability being span-based PDCCH monitoring, the configuring step includes configuring the first CC to monitor PDCCH candidates using both slot-based PDCCH monitoring and span-based PDCCH monitoring.
6. The communication method according to claim 1, in: Based on the first capability comprising a first rank and a first modulation order and the second capability comprising a second rank and a second modulation order, the configuring step comprises configuring the first CC using a lower of the first rank and the second rank and a lower of the first modulation order and the second modulation order.
7. The communication method according to claim 1, in: Based on the first capability including a first rank and a first modulation order and the second capability including a second rank and a second modulation order, the configuration step includes: configuring the first CC to receive a first physical downlink shared channel PDSCH using the first capability and a second physical downlink shared channel PDSCH using the second capability.
8. The communication method according to claim 1, in: The declaration of the capability includes declaring one of two capabilities for each of N CCs including a first CC and a second CC, wherein N is an integer greater than 2, and the step of declaring one of the two capabilities for each of N CCs including the first CC and the second CC includes declaring a first capability for a first subset of the N CCs and declaring a second capability for a second subset of the N CCs; and The steps of the configuration include: The network configures k CCs of the N CCs for the UE, where k is a positive integer, and p CCs of the k CCs are configured, by the network, with a configuration that exceeds both a first capability and a second capability, wherein p is equal to the smaller of k and Nk.
9. A communication method, include: Sending, by a user equipment UE, a capability declaration to a network, the capability declaration comprising a first capability declaration for a first component carrier CC and a second capability declaration for a second CC; as well as configuring, by the UE in response to a configuration command received from the network, one or more CCs including the first CC but not including the second CC, The configuring step comprises: configuring the first CC with a configuration exceeding the first capability, Wherein, based on the first capability being Capability 1 and the second capability being Capability 2, the configuring step includes: configuring the first CC to support both Capability 1 and Capability 2.
10. The communication method according to claim 9, in, The configuring step further includes configuring the first CC to support a capability selected from the group consisting of: overlapping physical downlink shared channel PDSCH, overlapping physical uplink shared channel PUSCH, out-of-order PDSCH, out-of-order PUSCH, and out-of-order hybrid automatic repeat request HARQ.
11. The communication method according to claim 9, in: Based on the first capability being Capability 2 and the second capability being Capability 2, the configuring step includes configuring the first CC to support out-of-order hybrid automatic repeat request HARQ between overlapping Capability 2 physical downlink shared channels PDSCH.
12. The communication method according to claim 9, in: Based on the first capability being single receiving and transmitting point TRP operation and the second capability being single receiving and transmitting point TRP operation, the configuration step includes configuring the first CC to support multiple receiving and transmitting point M-TRP operation.
13. The communication method according to claim 9, in: Based on the first capability being slot-based Physical Downlink Control Channel (PDCCH) monitoring and the second capability being span-based PDCCH monitoring, the configuring step includes configuring the first CC to monitor PDCCH candidates using both slot-based PDCCH monitoring and span-based PDCCH monitoring.
14. The communication method according to claim 9, in: Based on the first capability comprising a first rank and a first modulation order and the second capability comprising a second rank and a second modulation order, the configuring step comprises configuring the first CC using a lower of the first rank and the second rank and a lower of the first modulation order and the second modulation order.
15. The communication method according to claim 9, in: Based on the first capability including a first rank and a first modulation order and the second capability including a second rank and a second modulation order, the configuration step includes: configuring the first CC to receive a first physical downlink shared channel PDSCH using the first capability and a second physical downlink shared channel PDSCH using the second capability.
16. The communication method according to claim 9, in: The declaration of the capability includes declaring one of two capabilities for each of N CCs including a first CC and a second CC, wherein N is an integer greater than 2, and the step of declaring one of the two capabilities for each of N CCs including the first CC and the second CC includes: declaring a first capability for a first subset of the N CCs and declaring a second capability for a second subset of the N CCs; and The steps of the configuration include: The UE configures k CCs among the N CCs, where k is a positive integer, and p CCs of the k CCs are configured, by the UE, with a configuration that exceeds both a first capability and a second capability, wherein p is equal to the smaller of k and Nk.
17. The communication method according to claim 16, in, k is less than one-half of N.
