Resource Determination in Wireless Communication

Abstract

This application relates to methods, systems, and devices related to digital wireless communication, and more particularly, to techniques related to digital wireless communication, and more particularly, to techniques related to maintaining a PDCCH blind detection budget in a case where a cell can be scheduled by another cell and itself. In one exemplary aspect, a method for wireless communication is disclosed. The method includes: receiving, by a terminal on a primary scheduling cell, control information for a first cell according to a rule that a blind detection resource amount for the first cell does not exceed a budget, where the first cell is scheduled by the primary scheduling cell and the first cell is also scheduled by itself.

Description

Technical Field

[0001] This patent application generally relates to wireless communication. Background Art

[0002] Mobile communication technology is pushing the world towards an increasingly interconnected and networked society. The rapid growth of mobile communication and the progress in technology have led to a greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency, are also important for meeting the requirements of various communication scenarios. Various technologies are being discussed, including new methods for providing higher quality services. Summary of the Invention

[0003] This application discloses methods, systems, and devices related to digital wireless communication, and more specifically, discloses techniques related to maintaining the PDCCH blind detection budget in the case where a cell can be scheduled by another cell and itself.

[0004] In one exemplary aspect, a method for wireless communication is disclosed. The method includes: a terminal receiving control information for a first cell on a master scheduling cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, where the first cell is scheduled by the master scheduling cell and the first cell is also scheduled by itself.

[0005] In another exemplary aspect, a wireless communication device including a processor is disclosed. The processor is configured to implement the methods described herein.

[0006] In yet another exemplary aspect, the various techniques described herein can be embodied as processor-executable code and stored on a computer-readable program medium.

[0007] Details of one or more embodiments are set forth in the accompanying additional sections, drawings, and the following description. Other features will become apparent from the specification, drawings, and according to the claims. Brief Description of the Drawings

[0008] Figure 1 Shows a first example of CA scheduling.

[0009] Figure 2 Illustrates a second example of CA scheduling.

[0010] Figure 3 Shows an example method for maintaining the PDCCH blind detection budget in the case where a cell can be scheduled by another cell and itself.

[0011] Figure 4 Shows an example of a wireless communication system in which the techniques according to one or more embodiments of the present technology can be applied.

[0012] Figure 5 A block diagram representation that is part of a hardware platform. Detailed implementation

[0013] The development of the new generation of wireless communication - 5G New Radio (NR) communication - is part of a continuous mobile broadband evolution process to meet the growing network requirements. NR will provide greater throughput to allow more users to connect simultaneously. Other aspects such as energy consumption, device cost, spectral efficiency, and latency are also important for meeting the requirements of various communication scenarios.

[0014] The fourth-generation mobile communication technology (4G) Long-Term Evolution (LTE) or LTE-Advanced (LTE-A) and the fifth-generation mobile communication technology (5G) are facing increasing demands. Based on the current development trends, 4G and 5G systems are being developed to support enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) functions. Further, the spectrum used for 4G can be reused in 5G through dynamic spectrum sharing (DSS).

[0015] In the current 5G system, an SCell can be the only serving cell or a scheduled cell, while a PCell (or SCell) can include a serving cell and may or may not be a scheduled cell. In the case where a PCell (or SCell) can be a scheduled cell, the total PDCCH blind detection budget may not be changed. The serving cell is responsible for scheduling transmissions from and to the network over the wireless medium.

[0016] For the fifth-generation mobile communication technology, the physical downlink control channel (PDCCH) of the primary cell (PCell) (or the primary and secondary cell group cell (PSCell)) can schedule the physical downlink shared channel (PDSCH) or the physical uplink shared channel (PUSCH) on the PSCell. However, the PDSCH or PUSCH on the P(S)Cell may not be scheduled by the PDCCH of the SCell. Considering DSS in NR, the resources for the PDCCH of the PCell / SCell may be limited. To offload the PCell / SCell PDCCH, NR PDCCH enhancements for cross-carrier scheduling can be introduced, including the PDCCH for the SCell to schedule the PDSCH or PUSCH on the P(S)Cell. In particular, the total PDCCH blind detection budget can remain unchanged.

[0017] System Overview

[0018] In the case where the P(S)Cell is the scheduled cell (or the scheduling cell), the total PDCCH blind detection budget can remain unchanged. The total PDCCH blind detection budget can include at least two parameters, which will be discussed in more detail below.

[0019] In the case where the P(S)Cell is scheduled by the SCell, candidates for monitoring to avoid an increase in the PDCCH blind detection budget / complexity can be determined based on any of the methods described below.

[0020] The first method can include: when the UE supports search space sharing for DL (UL), at least one scheduled SCell with the same size as the DCI format 0_1 / 1_1 on the PCell can be configured. For the PDCCH blind detection of the scheduled PCell and the scheduled SCell on the scheduling cell, the blind detection is only performed in the USS (UE specific search space) for the scheduled SCell.

[0021] The second method may include: configuring M1 candidates for self-scheduling and M2 candidates for cross-carrier scheduling for the same cell. This may include candidates configured in a search space that are for self-scheduling and also for cross-carrier scheduling. This may also include candidates configured in a search space that are used for cross-carrier scheduling in addition to the candidates configured for self-scheduling. This may also include candidates configured in a search space that are only used for cross-carrier scheduling or for self-scheduling. Additionally, all candidates for USS may include candidates of nrofCandidates (if any) and nrofCandidates-r17 (if any).

[0022] The third method may include configuring (or predefining) an order for blind detection for the cell. The order of blind detection may include first performing self-scheduling blind detection and then performing cross-carrier scheduling blind detection. The order may also include first performing cross-carrier scheduling blind detection and then performing self-scheduling blind detection. Self-scheduling and cross-carrier scheduling may both be supported for the cell.

[0023] The fourth method may include that candidates for monitoring for cross-carrier scheduling for a P(S)Cell are counted among candidates for monitoring for self-scheduling for an SCell.

[0024] In the case where the P(S)Cell can be scheduled by the SCell, maintaining the number of cells of the P(S)Cell as 1 for both self-scheduling and cross-carrier scheduling includes one of the following methods. The first method may include that the PCell is counted as only one cell as the serving cell for the PCell or as the scheduled cell for its serving cell. The second method may include that the PCell is counted as the P1 cell as the serving cell for the PCell and as the P2 cell as the scheduled cell for its serving cell. In this case, P1 and P2 may be equal to 1. P1 and P2 may be determined by one of the following schemes. The first scheme may include P1 / P2 = M1 / M2, where M1 is the candidate for self-scheduling and M2 is the candidate for cross-carrier scheduling for the same cell. The second scheme may include configuring P1 and / or P2.

[0025] There may be two PDCCH blind detection parameters, one may include or and the other may include or For each scheduled cell, it may not be required that the UE monitors multiple PDCCH candidates or more than Non-overlapping CCEs. The budget can be at least two parameters.

[0026] Table 1 provided below provides, for a UE operating with a single serving cell, on a DL BWP with SCS configuration μ, the maximum number of monitored PDCCH candidates per slot.

[0027]

[0028] Table 1: Maximum number of monitored PDCCH candidates per slot for a DL BWP with SCS configuration μ ∈ {0, 1, 2, 3} for a single serving cell

[0029] Table 2 may provide the maximum number of non-overlapping CCEs per slot that a UE is expected to monitor for a corresponding set of PDCCH candidates, on a DL BWP with SCS configuration μ, and for a single serving cell.

[0030] If the CCEs of the PDCCH candidates correspond to different CORESET indices, or to different first symbols received for the respective PDCCH candidates, they may be non-overlapping.

[0031]

[0032] Table 2: Maximum number of non-overlapping CCEs per slot for a DL BWP with SCS configuration μ ∈ {0, 1, 2, 3} for a single serving cell

[0033] If the UE is configured with downlink cells, while the DL BWP has SCS configuration μ, where for each scheduled cell, it may not be required that the UE monitors more than PDCCH candidates or more than non-overlapping CCEs per slot on the active DL BWP of the serving cell.

[0034] If the UE is configured with downlink cells, while the DL BWP has SCS configuration μ, where the DL BWP of the active cell is the active DL BWP of the active cell, and the DL BWP of the deactivated cell is the DL BWP having the index provided by the firstActiveDownlinkBWP-Id of the deactivated cell, then it may not be required that the UE monitors on the DL BWP from On one or more active DL BWPs of one or more calling cells of a downlink cell, each time slot monitors more than PDCCH candidates or more than non-overlapping CCEs.

[0035] For each scheduled cell, it may not be required that the UE monitors more than PDCCH candidates or more than non-overlapping CCEs on the active DL BWP of the calling cell with SCS configuration μ per time slot.

[0036] For all search space sets within time slot n, let S css represent the set of CSS (Common Search Space) sets with cardinality I css , and let S uss represent the set of USS sets with cardinality J uss . The position of the USS set s j (0 ≤ j < J uss ) in S uss can be arranged in ascending order of the search space set index.

[0037] For the CSS set S css (j), let represent the counted number of PDCCH candidates for monitoring, and for the USS set S uss (j), let represent the counted number of PDCCH candidates for monitoring.

[0038] For the CSS set, within one time slot, the UE can monitor a total of non-overlapping CCEs of PDCCH candidates.

[0039] The UE can allocate the PDCCH candidates for monitoring to the USS set for the primary cell according to the following pseudocode. The primary cell has an active DL BWP with SCS configuration μ in time slot n. In the absence of allocated PDCCH candidates for monitoring, the UE may not expect to monitor the PDCCH in the USS set. This may indicate that all the configured candidates in this USS are discarded.

[0040] Let V CCE (S uss (j)) represent the set of non-overlapping CCEs for the search space set S uss (j), and let represent V CCE (S uss(j)), where the allocated PDCCH candidates for monitoring for the CSS set and for all search space sets S can be considered uss (k) (0 ≤ k ≤ j) of the allocated PDCCH candidates for monitoring, the non-overlapping CCEs for the search space set S uss (j) can be determined.

[0041] Set

[0042] Set

[0043] Set j = 0

[0044] while AND

[0045] allocate PDCCH candidates for monitoring to USS set S uss (j)

[0046]

[0047]

[0048] j = j + 1;

[0049] end while

[0050] In the case where the P(S)Cell can be the scheduled cell (which can also be the scheduling cell), the total PDCCH blind detection budget in each time slot can be greater than PDCCH candidates or more than non-overlapping CCEs. This may be because, for cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapping CCEs can be separately counted in each time slot.

[0051] Although candidates are used as examples representing the PDCCH blind detection budget in the following embodiments, as described herein, similar non-overlapping CCEs can also be applied.

[0052] The embodiments described below can show embodiments for preventing an increase in the PDCCH blind detection budget in the case where the P(S)Cell is the scheduled cell.

[0053] Example 1

[0054] In the case where search space sharing for DL (UL) is supported by the UE, at least one scheduled SCell with the same size as DCI format 0_1 / 1_1 on the PCell can be configured. For PDCCH blind detection for the scheduled PCell and the scheduled SCell on the serving cell, blind detection in the USS for the scheduled SCell can be performed.

[0055] In a carrier aggregation scenario, the configured P(S)Cell (named cell A) can be scheduled by the SCell (named cell B). For cell B, cell B can be configured as the serving cell and support serving cell A. Cell A can be scheduled on serving cell B with CIF = X, where X can be a value in the set [1,..., 7] or [0,..., 7].

[0056] For PDCCH blind detection for the P(S)Cell, this can include blind detection (BD) for scheduling the P(S)Cell itself when the P(S)Cell is the serving cell, and BD for scheduling the P(S)Cell when the serving cell is cell B. To avoid increasing the PDCCH blind detection budget, the scheme described below can be utilized.

[0057] Cell A and other N serving cells scheduled by cell B can be configured, where N can include an integer greater than 0. Figure 1 It is a block diagram 100 showing the first exemplary CA scheduling process. For at least one (named cell C) of the N cells ( Figure 1 where N = 2), CIF = Y is configured for cell C, and the size of DCI format 0_1 / 1_1 for serving cell C can be the same as the size of DCI format 0_1 / 1_1 for serving cell A. At the same time, the UE can support search space sharing through an indication via searchSpaceSharingCA-UL or via searchSpaceSharingCA-DL. For PDCCH blind detection for the scheduled PCell and the scheduled SCell on the serving cell, blind detection can only be performed in the USS for the scheduled SCell. The DCI format can be DCI format 0_1 or 1_1, or it can be DCI format 0_2 or 1_2.

[0058] In some embodiments, the UE can support uplink search space sharing through an indication via searchSpaceSharingCA-UL.

[0059] For the serving cell B, cell A with CIF = 1 and cell C with CIF = 2 can be scheduled by cell B. The size of DCI format 0_1 for serving cell A can be the same as the size of DCI format 0_1 for serving cell C. Then, for the PDCCH blind detection for cell A and cell C on the serving cell, the blind detection can only be performed in the USS determined by CIF = 2 for cell C. In this way, using search space sharing, the DCI with CIF = 1 can also be detected in the USS determined by CIF = 2. For cell A, when cell A is the serving cell, the PDCCH blind detection can also be performed. The total PDCCH blind detection budget may not increase.

[0060] In some embodiments, when the DCI sizes for scheduling SCell and for scheduling P(S)Cell through search space sharing may be the same, the blind detection is only performed in the USS for the scheduled SCell. Implementing the blind detection for P(S)Cell may only include the blind detection for P(S)Cell when P(S)Cell is the serving cell, and does not include the blind detection for P(S)Cell when P(S)Cell is the scheduled cell. Then, when supporting the scheduling of P(S)Cell by SCell, the total PDCCH blind detection budget may not increase. The complexity of the UE's blind detection may not increase.

[0061] Example 2

[0062] The second embodiment may involve configuring M1 candidates for self-scheduling and M2 candidates for cross-carrier scheduling for the same cell. Such a configuration may include at least one of the following: the candidates configured in the search space are used for self-scheduling and are also used for cross-carrier scheduling; the candidates configured in the search space are used for cross-carrier scheduling in addition to the candidates configured for self-scheduling; the candidates configured in the search space are only used for cross-carrier scheduling or for self-scheduling. In addition, all candidates for the USS may include the candidates of nrofCandidates (if any) and nrofCandidates-r17 (if any).

[0063] In the carrier aggregation scenario, the configured P(S)Cell (named cell A) can be scheduled by the SCell (named cell B). For cell B, the configured cell B can be the serving cell and can support serving cell A. Cell A can be scheduled on serving cell B with CIF = X, where X includes a value in the set [1,..., 7] or [0,..., 7].

[0064] For the PDCCH blind detection for the P(S)Cell, it includes the BD for scheduling the P(S)Cell itself when the P(S)Cell is the primary scheduling cell, and the BD for scheduling the P(S)Cell when the primary scheduling cell can be cell B. In order not to increase the PDCCH blind detection budget, the scheme described below can be utilized.

[0065] For the P(S)Cell, M1 candidates for self-scheduling and M2 candidates for cross-carrier scheduling for the same cell can be configured. The configuration method can include at least one of the following: the candidates configured in the search space are used for self-scheduling and also for cross-carrier scheduling (e.g., USS), for the P(S)Cell, only nrofCandidates can be configured for both self-scheduling and cross-carrier scheduling; the candidates configured in the search space are used for cross-carrier scheduling (e.g., USS) in addition to the candidates configured for self-scheduling, for the P(S)Cell, nrofCandidates can be configured for self-scheduling, and nrofCandidates-r17 is configured for cross-carrier scheduling; the candidates configured in the search space are only used for cross-carrier scheduling (e.g., USS), for the P(S)Cell, nrofCandidates can be configured for self-scheduling, or nrofCandidates-r17 can be configured for cross-carrier scheduling. In addition, when M1 + M2 = M, the candidates do not need to be discarded at that time, otherwise candidate discarding can be expected. This can indicate that all candidates for USS can include the candidates of nrofCandidates (if any) and nrofCandidates-r17 (if any). After candidate discarding, the total PDCCH blind detection budget may not increase.

[0066] Among them, nrofCandidates is configured by the following signaling structure and is similar to nrofCandidates-r17.

[0067]

[0068]

[0069] In one embodiment, in the case where the P(S)Cell is not supported to be scheduled by the SCell, a Common Search Space (CSS) #0 with 6 candidates (6 BDs), a CSS #1 with 6 candidates (6 BDs), and a UE Specific Search Space (USS) #2 with 16 candidates (32 BDs) can be configured, with a total of 44 BDs. At the same time, the subcarrier spacing (SCS) includes 15 kHz for the P(S)Cell, that is, μ = 0. The candidates of nrofCandidates configured in the search space can be used as candidate resources. After multiplying by the number of different-sized DCI formats that can be carried by the candidates, the number of BDs is obtained, which is also referred to as the candidates for monitoring. For example, in the CSS, there may be only one size of DCI format, then the number of BDs can be equal to the number of candidates. For example, in the USS, there are two sizes of DCI formats, then the number of BDs can be twice the number of candidates.

[0070] In the case where the P(S)Cell supports being scheduled by the SCell, a CSS #0 with 6 candidates (6 BDs), a CSS #1 with 6 candidates (6 BDs), and a USS #2 with 16 candidates (32 BDs) can be configured. Then, the BDs for the USS #2 for self-scheduling can include 32, and the BDs for the USS #2 for cross-carrier scheduling are 32, with a total of 76 BDs, which can be greater than the PDCCH blind detection budget. To avoid exceeding the budget, one of the following methods can be used.

[0071] The first method can include that for the USS #2, only nrofCandidates can be configured for both self-scheduling and cross-carrier scheduling for the P(S)Cell. If all candidates of nrofCandidates are 8 (i.e., 16 BDs), then there may be 16 BDs for cross-carrier scheduling and 6 + 6 + 16 = 28 BDs for self-scheduling. The total BDs for the P(S)Cell can be 44 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring the USS #2 can be 16 + 16 = 32, and assuming μ = 0 and may not be discarded in some cases. If all candidates of nrofCandidates are 10 (i.e., 20 BDs), there may be 20 BDs for cross-carrier scheduling and 6 + 6 + 20 = 32 BDs for self-scheduling. The total BDs for P(S)Cell can be 52 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 20 + 20 = 40, and may not be discarded under the assumption that μ = 0 and may be discarded in some cases.

[0072] In the second method, for USS#2, the candidates configured in the search space, in addition to the candidates configured for self-scheduling, can also be used for cross-carrier scheduling. If all candidates of nrofCandidates are 6 (i.e., 12 BDs) and all candidates of nrofCandidates-r17 are 10 (i.e., 20 BDs), there may be 20 BDs for cross-carrier scheduling and 6 + 6 + 12 = 24 BDs for self-scheduling. The total BDs for P(S)Cell can be 44 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 12 + 20 = 32, and may not be discarded under the assumption that μ = 0 and In some cases. If all candidates of nrofCandidates are 8 (i.e., 16 BDs) and all candidates of nrofCandidates-r17 are 10 (i.e., 20 BDs), there may be 20 BDs for cross-carrier scheduling and 6 + 6 + 16 = 28 BDs for self-scheduling. The total BDs for P(S)Cell can be 48 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 16 + 20 = 36, and may not be discarded under the assumption that μ = 0 and In some cases may not be discarded.

[0073] In the third method, for USS, the candidates configured in the search space can be used for self-scheduling or for cross-carrier scheduling. If all the candidates of nrofCandidates are 6 (i.e., 12 BDs) configured for USS#2 for self-scheduling, and all the candidates of nrofCandidates-r17 are 10 (i.e., 20 BDs) configured for USS#3 for cross-carrier scheduling, then there may be 20 BDs for cross-carrier scheduling and 6 + 6 + 12 = 24 BDs for self-scheduling. The total BDs for the P(S)Cell can be 44 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 12, and the candidates for monitoring USS#3 can be 20. In the case where μ = 0 and neither USS#2 nor USS#3 may be discarded. If all the candidates of nrofCandidates are 8 (i.e., 16 BDs) configured for USS#2 for self-scheduling, and all the candidates of nrofCandidates-r17 are 10 (i.e., 20 BDs) configured for USS#3 for cross-carrier scheduling, then there may be 20 BDs for cross-carrier scheduling and 8 + 6 + 16 = 28 BDs for self-scheduling. The total BDs for the P(S)Cell can be 48 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 16, and the candidates for monitoring USS#3 can be 20. Then, in the case where μ = 0 and USS#2 may not be discarded, but USS#3 will be discarded. Therefore, USS#3 may not be used for cross-carrier scheduling of the P(S)Cell, which may indicate that cross-carrier scheduling of the P(S)Cell by the SCell through USS#3 may not be supported. If all the candidates of nrofCandidates-r17 are 8 (i.e., 16 BDs) configured for USS#2 for cross-carrier scheduling, and all the candidates of nrofCandidates are 10 (i.e., 20 BDs) configured for USS#3 for self-scheduling, then there may be 16 BDs for cross-carrier scheduling and 8 + 6 + 20 = 28 BDs for self-scheduling. The total BDs for the P(S)Cell can be 48 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 can be 16, and the candidates for monitoring USS#3 can be 20. Then, in the case where μ = 0 and In this case, USS#2 may not be discarded, but USS#3 will be discarded. Therefore, USS#2 can be used for cross-carrier scheduling of the P(S)Cell, which means that the P(S)Cell can be supported to be scheduled by the SCell via USS#2.

[0074] In one embodiment, the candidates configured in the search space can be used for cross-carrier scheduling and can only be configured on the P(S)Cell. In another embodiment, in the case where there is at least one USS and the candidates configured in this USS for cross-carrier scheduling are valid candidates for monitoring, the P(S)Cell can be scheduled by the SCell.

[0075] In one embodiment, support for both self-scheduling and cross-carrier scheduling of the P(S)Cell is achieved by including the valid USS for cross-carrier scheduling of the P(S)Cell after discarding the candidates in all the configured search spaces. Then, in the case where the P(S)Cell is supported to be scheduled by the SCell, the total PDCCH blind detection budget may not increase. The complexity of the UE's blind detection may not increase.

[0076] Example 3

[0077] The third embodiment may include predefining / configuring the order of blind detection for the cell. The order of blind detection may include first performing self-scheduling blind detection and then performing cross-carrier scheduling blind detection; or first performing cross-carrier scheduling blind detection and then performing self-scheduling blind detection. The cell can support both self-scheduling and cross-carrier scheduling.

[0078] In the carrier aggregation scenario, the configured P(S)Cell (named cell A) can be scheduled by the SCell (named cell B). For cell B, cell B can be configured as the scheduling cell and support the scheduling cell A. Cell A can be scheduled on the scheduling cell B with CIF = X, where X can be a value in the set [1,..., 7] or [0,..., 7].

[0079] For the PDCCH blind detection of the P(S)Cell, it includes the BD for scheduling the P(S)Cell itself in the case where the P(S)Cell is the scheduling cell, and the BD for scheduling the P(S)Cell in the case where the scheduling cell is cell B. In order not to increase the PDCCH blind detection budget, the following schemes can be utilized.

[0080] In one embodiment, for a P(S)Cell, if the predefined / configured blind detection order includes first performing self-scheduling blind detection and then performing cross-carrier scheduling blind detection, candidate discarding may be first performed on the USSs configured with candidates for self-scheduling. Thereafter, the remaining part of the blind detection budget may be used for candidate discarding for the USSs configured with candidates for cross-carrier scheduling. In the case where there is at least one USS and the candidates configured in the USS for cross-carrier scheduling are valid candidates for monitoring, the P(S)Cell may be scheduled by an SCell.

[0081] In one embodiment, for a P(S)Cell, if the predefined / configured blind detection order includes first performing cross-carrier scheduling blind detection and then performing self-scheduling blind detection, candidate discarding may be first performed on the USSs configured with candidates for cross-carrier scheduling. Thereafter, the remaining part of the blind detection budget may be used for candidate discarding for the USSs configured with candidates for self-scheduling. In the case where there is at least one USS and the candidates configured in the USS for cross-carrier scheduling are valid candidates for monitoring, the P(S)Cell may be scheduled by an SCell. The USSs with candidates configured for self-scheduling may include valid candidates for monitoring and may be used for self-scheduling blind detection of the P(S)Cell.

[0082] The configuration method for candidates for cross-carrier scheduling may include any one of the following: the candidates configured in the search space may be used for self-scheduling and may also be used for cross-carrier scheduling; the candidates configured in the search space, in addition to the candidates configured for self-scheduling, may also be used for cross-carrier scheduling; the candidates configured in the search space are only used for cross-carrier scheduling or for self-scheduling. After candidate discarding in the order of blind detection of the cell, the PDCCH blind detection complexity may not increase.

[0083] In one embodiment, in the case where the P(S)Cell is not supported to be scheduled by an SCell, CSS#0 with 6 candidates (6 BDs), CSS#1 with 6 candidates (6 BDs), and CSS#2 with 16 candidates (32 BDs) are configured, and the total is 44 BDs. At the same time, it is assumed that the subcarrier spacing (SCS) for the P(S)Cell may be 15 kHz, that is, μ = 0. The number of candidates of nrofCandidates that can be configured in the search space, as the candidate resources, multiplied by the number of different sizes of DCI formats that can be carried by the candidates, gives the number of BDs, which is also referred to as the candidates for monitoring. For example, if there is only one size of DCI format in the CSS, then the number of BDs is equal to the number of candidates. As another example, if there are two sizes of DCI formats in the USS, then the number of BDs is twice the number of candidates.

[0084] When the P(S) Cell supports being scheduled by the SCell, configure CSS#0 with 6 candidates (6 BDs), CSS#1 with 6 candidates (6 BDs), CSS#2 with 6 candidates (12 BDs), and CSS#4 with 6 candidates (12 BDs) for self-scheduling; configure CSS#3 with 4 candidates (8 BDs) and CSS#4 with 4 candidates (8 BDs) for cross-carrier scheduling (which means being scheduled by the SCell). Then the total is 52 BDs, which is greater than the PDCCH blind detection budget. To avoid exceeding the budget, one of the following methods can be used.

[0085] In the first method, if the predefined / configured order of blind detection includes first performing self-scheduling blind detection and then performing cross-carrier scheduling blind detection, candidate discarding can be first performed on the USSs configured with candidates for self-scheduling. For candidate discarding in the time slots with all the above search spaces, the remaining part of the blind detection budget is 44 - (6 + 6 + 12 + 12) = 8 (assuming μ = 0 and ). There can be no overbooking. The remaining part in the blind detection budget can be used for candidate discarding for the USSs configured with candidates for cross-carrier scheduling. In the case where there is at least one USS and the candidates configured in this USS for cross-carrier scheduling are valid candidates for monitoring, the P(S) Cell can be scheduled by the SCell. After candidate discarding, USS#3 can be valid while USS#5 is discarded. Therefore, USS#3 can be used for cross-carrier scheduling of the P(S) Cell, which means that the P(S) Cell can be supported to be scheduled by the SCell through USS#3.

[0086] In the second method, if the predefined / configured order of blind detection includes first performing cross-carrier scheduling blind detection and then performing self-scheduling blind detection, candidate discarding can be first performed on the USSs configured with candidates for cross-carrier scheduling. For candidate discarding in the time slots with all the above search spaces, the remaining part of the blind detection budget can be 44 - (8 + 8) = 28 (assuming μ = 0 and) Overbooking may not exist. The P(S)Cell may be scheduled by the SCell. The remaining part of the blind detection budget may be used for candidate discarding for the USS that configures candidates for self-scheduling. After candidate discarding, USS#2 may be valid while USS#4 may be discarded. Therefore, USS#3 and USS#5 may be used for cross-carrier scheduling for the P(S)Cell, which means that the P(S)Cell can be scheduled by the SCell with the support of USS#3. CSS#0, CSS#1, and USS#2 may be used for self-scheduling of the P(S)Cell, which means that USS#4 can be discarded and may not be used for self-scheduling of the P(S)Cell.

[0087] In one embodiment, if the predefined / configured order of blind detection includes first performing cross-carrier scheduling blind detection and then performing self-scheduling blind detection, to ensure that the CSS is always valid, the additional configuration may include one of the following. In the case where the candidates configured in the search space are used for self-scheduling and also for cross-carrier scheduling, it may not be desirable for all candidates in the entire search space to be greater than the PDCCH blind detection budget. In the case where the candidates configured in the search space are used for cross-carrier scheduling in addition to the candidates configured for self-scheduling, then it may not be desirable for all candidates in all CSSs and all search spaces with candidates for cross-carrier scheduling to be greater than the PDCCH blind detection budget. In the case where the candidates configured in the search space are only used for cross-carrier scheduling or only used for self-scheduling, it may not be desirable for all candidates in all CSSs and all search spaces with candidates for cross-carrier scheduling to be greater than the PDCCH blind detection budget.

[0088] In one embodiment, the candidates configured in the search space are used for cross-carrier scheduling and can only be configured on the P(S)Cell. In one embodiment, in the case where there is at least one USS and the candidates configured in this USS for cross-carrier scheduling are valid candidates for monitoring, the P(S)Cell may be scheduled by the SCell.

[0089] In one embodiment, by predefining / configuring the order of blind detection for the cell under the limitation of the PDCCH blind detection budget, both self-scheduling and cross-carrier scheduling can be supported for the P(S)Cell. Then, in the case where the P(S)Cell is supported to be scheduled by the SCell, the total PDCCH blind detection budget may not increase. The complexity of the UE's blind detection may not increase.

[0090] Example 4

[0091] Candidates for monitoring can be used for cross-carrier scheduling for the P(S)Cell and are counted as candidates for monitoring for self-scheduling for the SCell. In a carrier aggregation scenario, the configured P(S)Cell (named cell A) can be scheduled by the SCell (named cell B). For cell B, configuring cell B can include the primary scheduling cell and support the primary scheduling cell A. Cell A can be scheduled on the primary scheduling cell B with CIF = X, where X can include a value from the set [1,..., 7] or [0,..., 7].

[0092] For PDCCH blind detection for the P(S)Cell, it includes the BD for scheduling the P(S)Cell itself when the P(S)Cell can include the primary scheduling cell, and the BD for scheduling the P(S)Cell when the primary scheduling cell can be cell B. To avoid increasing the PDCCH blind detection budget, the following schemes can be used.

[0093] For the P(S)Cell, the blind detection for the P(S)Cell only includes the blind detection for the P(S)Cell when the P(S)Cell can be the primary scheduling cell. The blind detection for the P(S)Cell when the P(S)Cell can be the scheduled cell is counted as a candidate for monitoring for self-scheduling for the SCell (also called blind detection). The P(S)Cell can be scheduled by the SCell.

[0094] Candidate overbooking / discard can only be performed on the primary cell. All candidates for SCell monitoring may not exceed the PDCCH blind detection budget. As a result, it may not be desirable for the candidates for monitoring for cross-carrier scheduling for the P(S)Cell plus the candidates for monitoring for self-scheduling for the SCell to exceed the PDCCH blind detection budget.

[0095] In one embodiment, when the P(S)Cell is not supported to be scheduled by the SCell, CSS#0 with 6 candidates (6 BDs), CSS#1 with 6 candidates (6 BDs), and CSS#2 with 16 candidates (32 BDs) can be configured, with a total of 44 BDs, assuming that the subcarrier spacing (SCS) for the P(S)Cell is 15 kHz, that is, μ = 0. The candidates of nrofCandidates that can be configured in the search space as candidate resources, multiplied by the number of different-sized DCI formats that can be carried by the candidates, result in the number of BDs, which is also called the candidates for monitoring. For example, if there is only one size of DCI format in the CSS, then the number of BDs is equal to the number of candidates. For example, if there are two sizes of DCI formats in the USS, then the number of BDs is twice the number of candidates.

[0096] When the P(S)Cell supports being scheduled by the SCell, CSS#0 with 6 candidates (6 BDs), CSS#1 with 6 candidates (6 BDs), USS#2 with 6 candidates (12 BDs), and USS#4 with 6 candidates (12 BDs) can be configured for self-scheduling; USS#3 with 8 candidates (16 BDs) can be configured for cross-carrier scheduling (scheduled by the SCell). The total can be 52 BDs, which may be greater than the PDCCH blind detection budget. To avoid exceeding the budget, the following method can be adopted.

[0097] The candidates for monitoring used for cross-carrier scheduling for the P(S)Cell are counted among the candidates for monitoring used for self-scheduling for the SCell. It is not expected that the candidates for monitoring used for cross-carrier scheduling for the P(S)Cell plus the candidates for monitoring used for self-scheduling for the SCell will be greater than the PDCCH blind detection budget. For example, the search spaces configured on the SCell are USS#1 with 6 candidates (12 BDs) for self-scheduling, USS#2 with 4 candidates (8 BDs), and USS#3 with 4 candidates (8 BDs), plus 16 candidates for monitoring used for cross-carrier scheduling for the P(S)Cell, resulting in 28 + 16 = 44 BDs, and this result is not greater than the PDCCH blind detection budget (assuming μ = 0 and ). The blind detection for the P(S)Cell can only include the blind detection for the P(S)Cell when the P(S)Cell is the scheduling cell, and it will not be greater than the PDCCH blind detection either.

[0098] In one embodiment, the candidates for monitoring used for cross-carrier scheduling for the P(S)Cell are counted among the monitoring candidates for SCell self-scheduling, and it is ensured that the candidates for monitoring used for cross-carrier scheduling for the P(S)Cell plus the candidates for monitoring used for self-scheduling for the SCell are not greater than the PDCCH blind detection budget configured by the gNB, so as to support both self-scheduling and cross-carrier scheduling for the P(S)Cell. When the P(S)Cell supports being scheduled by the SCell, the total PDCCH blind detection budget may not increase. The complexity of the UE's blind detection may not increase.

[0099] Example 5

[0100] In the case where the P(S)Cell can be scheduled by the SCell, for both self-scheduling and cross-carrier scheduling, the number of cells of the P(S)Cell is 1. In the Carrier Aggregation (CA) scenario, configure the P(S)Cell (named Cell A) to be schedulable by the SCell (named Cell B). For Cell B, configure Cell B to be the scheduling cell and support the scheduling cell A. It can be assumed that Cell A is scheduled on the scheduling cell B with CIF = X, where X is a value in the set [1,..., 7] or [0,..., 7].

[0101] Figure 2 The block diagram 200 showing the second example CA scheduling process is presented. The cell can be configured to be scheduled by Cell 2 for Cells 1 to 6, where Cell 1 can be the PCell with μ = 0 and can be scheduled by Cell 2 with μ = 1. Cells 2 to 6 are SCell. The UE can report that its carrier aggregation capability is pdcch-BlindDetectionCA = 4 cells, which means Since the 6 configured cells may be greater than so CA scaling is expected. This can indicate that it is not necessary for the UE to monitor more than per time slot on one or more activated DL BWPs of one or more scheduling cells from PDCCH candidates.

[0102] In some cases, M_total_15khz = floor(4 * 44 * 1 / 6) = 29; M_total_30khz = floor(4 * 36 * 6 / 6) = 144. As a result, since the PCell is counted twice in the above calculation, the blind detection complexity may increase. This means that the blind detection budget may also be expanded compared to the case where the scheduled PCell is not supported. In the case where the PCell does not support being scheduled, M_total_15khz = floor(4 * 44 * 1 / 6) = 29; M_total_30khz = floor(4 * 36 * 5 / 6) = 120.

[0103] In one embodiment, in the case where the P(S)Cell can be scheduled by the SCell, for both self-scheduling and cross-carrier scheduling, maintaining the number of cells of the P(S)Cell as 1 can include one of the following methods.

[0104] The first method may include that the PCell is counted as the serving cell for the PCell or the scheduled cell for its serving cell is only counted as one cell. For example, if the PCell may only be counted into one cell as the serving cell for the PCell, then M_total_15khz = floor(4 * 44 * 1 / 6) = 29; M_total_30khz = floor(4 * 36 * 5 / 6) = 120. The blind detection complexity may not increase. The PDCCH blind detection budget may not increase.

[0105] In the second method, the PCell is counted as the P1 cell as the serving cell for the PCell and the P2 cell as the scheduled cell for its serving cell. In some cases, P1 + P2 = 1. P1 and P2 can be determined by one of the following schemes. The first scheme may include P1 / P2 = M1 / M2, where M1 is the candidate for self-scheduling and M2 is the candidate for cross-carrier scheduling for the same cell. For example, M1 = 22, M2 = 22, then P1 = 0.5, P2 = 0.5. Thus, in this example, M_total_15khz = floor(4 * 44 * 0.5 / 6) = 14; M_total_30khz = floor(4 * 36 * 5.5 / 6) = 132. The blind detection complexity may not increase. The PDCCH blind detection budget may not increase. The second scheme may include configuring P1 and / or P2. For example, configure P1 = 0.6, P2 = 0.4. Thus, in this example, M_total_15khz = floor(4 * 44 * 0.6 / 6) = 17; M_total_30khz = floor(4 * 36 * 5.4 / 6) = 129. The blind detection may not increase. The PDCCH blind detection budget may not increase.

[0106] In one embodiment, when the P(S)Cell can be scheduled by the SCell, the number of cells of the P(S)Cell is 1 for both self-scheduling and cross-carrier scheduling. This can allow the total PDCCH blind detection budget not to increase when the P(S)Cell is supported to be scheduled by the SCell and the number of configured cells is greater than the number of UEs reporting carrier aggregation capabilities. The blind detection complexity of the UE may not increase.

[0107] Figure 3Illustrates an example method 300 for maintaining a PDCCH blind detection budget in a case where a cell can be scheduled by another cell and itself. The method may include a terminal on a master scheduling cell receiving control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, where the first cell is scheduled by the master scheduling cell and the first cell is also scheduled by itself (block 302). The first cell may include a candidate cell to be scheduled by the master scheduling cell. The rule may specify that the PDCCH blind detection resources remain unchanged.

[0108] In some embodiments, the blind detection resources include the number of multiple candidate or non-overlapping control channel elements (CCEs) for physical downlink control channel (PDCCH) blind detection.

[0109] In some embodiments, the first cell includes one of a primary cell (PCell), a primary secondary cell group cell (PSCell), and a secondary cell (SCell).

[0110] In some embodiments, the rule further includes that a second cell different from the first cell includes a downlink control information (DCI) format size that is the same as the DCI format size of the first cell, where the terminal reports the ability to support search space sharing for downlink and / or uplink.

[0111] In some embodiments, the method includes: performing a blind detection process on the first cell on the master scheduling cell, where the master scheduling cell only includes the search space of the second cell.

[0112] In some embodiments, the rule further includes: configuring multiple candidates for self-scheduling and multiple candidates for cross-carrier scheduling for the first cell.

[0113] In some embodiments, multiple candidates in the search space are configured to be used for both self-scheduling and cross-carrier scheduling simultaneously.

[0114] In some embodiments, multiple candidates in the search space are respectively configured for self-scheduling and cross-carrier scheduling.

[0115] In some embodiments, multiple candidates in the search space are configured for self-scheduling or cross-carrier scheduling.

[0116] In some embodiments, the counted number of physical downlink control channel (PDCCH) candidates for monitoring the search space includes the combination of candidates for self-scheduling and candidates for cross-carrier scheduling.

[0117] In some embodiments, the rule further includes: determining an order for performing blind detection on the first cell, where the order is predefined or configured by higher layer signaling.

[0118] In some embodiments, the sequence includes first performing a self-scheduling blind detection process, followed by performing a cross-carrier scheduling blind detection process.

[0119] In some embodiments, before performing the cross-carrier scheduling blind detection process, the sequence includes using the remaining portion of the budget to count multiple candidates for monitoring.

[0120] In some embodiments, the sequence includes first performing the cross-carrier scheduling blind detection process, followed by performing the self-scheduling blind detection process.

[0121] In some embodiments, before performing the self-scheduling blind detection process, the sequence includes using the remaining portion of the budget to count multiple candidates for monitoring.

[0122] In some embodiments, the rule further includes: counting the candidates for monitoring the first cell for cross-carrier scheduling among the multiple candidates for monitoring the primary scheduling cell.

[0123] In some embodiments, the sum of the number of candidates for monitoring the first cell for cross-carrier scheduling and the number of candidates for monitoring the primary scheduling cell is not greater than the budget.

[0124] In some embodiments, the method includes maintaining the number of cells for the first cell as 1 cell for both self-scheduling and / or cross-carrier scheduling, or counting it as 2 cells for both self-scheduling and cross-carrier scheduling, where the number of cells is predefined or configured by higher layer signaling.

[0125] In some embodiments, the number of cells for the first cell is counted as 1 cell as the primary scheduling cell for the first cell or as the scheduled cell for the primary scheduling cell.

[0126] In some embodiments, counting the number of cells for the first cell as 1 cell includes: counting the first cell as cell P1 which is the primary scheduling cell for the first cell, and counting cell P2 as the scheduled cell for the primary scheduling cell, where the sum of the number of cells of P1 and P2 is equal to 1.

[0127] In some embodiments, P1 and P2 are configured by higher layer signaling, or implicitly derived from the number of candidates for self-scheduling and the number of candidates for cross-carrier scheduling for the first cell.

[0128] Example Wireless System

[0129] Figure 4Shows an example of a wireless communication system in which the techniques according to one or more embodiments of the present technology can be applied. The wireless communication system 400 may include one or more base stations (BS) 405a, 405b, one or more wireless devices 410a, 410b, 410c, 410d, and a core network 425. The base stations 405a, 405b may provide wireless services to the wireless devices 410a, 410b, 410c, and 410d in one or more wireless sectors. In some embodiments, the base stations 405a, 405b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors. The base station may implement the functions of a serving cell or a candidate cell as described in this application.

[0130] The core network 425 may communicate with one or more base stations 405a, 405b. The core network 425 provides connections to other wireless communication systems and wired communication systems. The core network may include one or more serving subscription databases to store information related to the subscribed wireless devices 410a, 410b, 410c, and 410d. The first base station 405a may provide wireless services based on a first radio access technology, while the second base station 405b may provide wireless services based on a second radio access technology. Depending on the deployment scenario, the base stations 405a and 405b may be co-located or may be installed separately on site. The wireless devices 410a, 410b, 410c, and 410d may support multiple different radio access technologies.

[0131] In some embodiments, the wireless communication system may include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices include two or more wireless technologies that can be used to connect different wireless networks.

[0132] Figure 5 Is a block diagram representation of a part of a hardware platform. A hardware platform 505 such as a network device or a base station or a wireless device (or UE) may include electronic devices 510 such as a processor, such as a microprocessor, that implements one or more of the techniques presented in this application. The hardware platform 505 may include transceiver electronics 515 to transmit and / or receive wireless signals through one or more communication interfaces, such as antennas 520. The hardware platform 505 may implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 505 may include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some embodiments, the processor electronics 510 may include at least a part of the transceiver electronics 515. In some embodiments, the disclosed techniques, modules, or functions are implemented using the hardware platform 505.

[0133] Conclusion

[0134] Based on the foregoing, it should be understood that, for purposes of illustration, specific embodiments of the presently disclosed technology have been described herein, but various modifications may be made without departing from the scope of the present invention. Accordingly, the presently disclosed technology is not limited except as restricted by the appended claims.

[0135] The disclosed and other embodiments, modules, and functional operations described in this application can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware including the structures disclosed in this application and their structural equivalents, or in a combination of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter implementing a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" encompasses all apparatuses, devices, and machines for processing data, including, by way of example, programmable processors, computers, or multiple processors or computers. In addition to hardware, the apparatus can include code that creates an execution environment for the computer programs being discussed, e.g., code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to an appropriate receiver apparatus.

[0136] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language (including compiled or interpreted languages), and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. The program can be stored in a part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), stored in a single file dedicated to the program being discussed, or stored in multiple cooperating files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program can be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0137] The processes and logical flows described in this specification can be performed by one or more programmable processors that execute one or more computer programs to perform functions by operating on input data and generating output. The processes and logical flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0138] By way of example, processors suitable for the execution of a computer program include both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to, one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data, to receive data from or transfer data to the one or more mass storage devices, or both. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, by way of example including semiconductor memory devices (such as, EPROM, EEPROM, and flash memory devices); magnetic disks (such as internal hard disks or removable disks); magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0139] Although this patent application contains many details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this patent application in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although the features may be described above as acting in certain combinations and even initially claimed as such, in some cases one or more features from a claimed combination can be excluded from the combination, and the claimed combination can be directed to a subcombination or a variation of a subcombination.

[0140] Similarly, although the operations are depicted in the drawings in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the operations shown be performed to obtain the desired result. Also, the separation of various system components in the embodiments described in this patent application should not be construed as requiring such separation in all embodiments.

[0141] Only a few embodiments and examples have been described, and other embodiments, enhancements, and variations can be made based on what is described and shown in this patent document.

Claims

1. A method for wireless communication, comprising: receiving, by a terminal, control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, where the budget includes a physical downlink control channel PDCCH candidate budget and a non-overlapping control channel element CCE budget; and when the first cell is scheduled by a master scheduling cell and the first cell is also scheduled by itself, the terminal only counts the first cell once to determine the budget.

2. The method according to claim 1, wherein the blind detection resources include a candidate set for physical downlink control channel PDCCH blind detection or the number of non-overlapping control channel elements CCEs.

3. The method according to claim 1, wherein the first cell includes one of a primary cell PCell, a primary and secondary cell group cell PSCell, and a secondary cell SCell.

4. The method according to claim 1, wherein, The rule further includes a candidate set for self-scheduling and a candidate set for cross-carrier scheduling respectively configured for the first cell.

5. The method according to claim 4, wherein, The candidate set in the search space is configured for self-scheduling or cross-carrier scheduling.

6. An apparatus for wireless communication, the apparatus includes a processor and a memory, the processor is configured to read instructions from the memory to perform the following operations: Receive control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, where The budget includes a physical downlink control channel PDCCH candidate budget and a non-overlapping control channel element CCE budget; and when the first cell is scheduled by a master scheduling cell and the first cell is also scheduled by itself, only count the first cell once to determine the budget.

7. The apparatus according to claim 6, wherein the blind detection resources include a candidate set for physical downlink control channel PDCCH blind detection or the number of non-overlapping control channel elements CCEs.

8. The apparatus according to claim 6, wherein the first cell includes one of a primary cell PCell, a primary and secondary cell group cell PSCell, and a secondary cell SCell.

9. The device according to claim 6, wherein, The rule further includes a candidate set for self-scheduling and a candidate set for cross-carrier scheduling respectively configured for the first cell.

10. The apparatus according to claim 9, wherein, The candidate set in the search space is configured for self-scheduling or cross-carrier scheduling.

11. A non-transitory computer-readable medium storing code thereon, the code when executed by a processor causes the processor to perform the following operations: Receive control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, where The budget includes a physical downlink control channel PDCCH candidate budget and a non-overlapping control channel element CCE budget; and when the first cell is scheduled by a master scheduling cell and the first cell is also scheduled by itself, only count the first cell once to determine the budget.

12. The non-transitory computer-readable medium according to claim 11, wherein the blind detection resources include a candidate set for physical downlink control channel PDCCH blind detection or the number of non-overlapping control channel elements CCEs.

13. The non-transitory computer-readable medium according to claim 11, wherein the first cell includes one of a primary cell (PCell), a primary-secondary cell group cell (PSCell), and a secondary cell (SCell).

14. The non-transitory computer-readable medium according to claim 11, wherein, The rules further include a candidate set configured for self-scheduling and a candidate set configured for cross-carrier scheduling for the first cell respectively.

15. The non-transitory computer-readable medium according to claim 14, wherein, The candidate set in the search space is configured for self-scheduling or cross-carrier scheduling.

16. A method for wireless communication, comprising: transmitting, by a base station, control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed a budget, wherein the budget includes a physical downlink control channel (PDCCH) candidate budget and a non-overlapping control channel element (CCE) budget, and wherein, when the first cell is scheduled by a primary scheduling cell and the first cell is also self-scheduled, the budget is determined by a terminal by counting only once for the first cell.

17. The method according to claim 16, wherein the blind detection resources include a candidate set for blind detection of a physical downlink control channel (PDCCH) or the number of non-overlapping control channel elements (CCEs).

18. The method according to claim 16, wherein the first cell includes one of a primary cell (PCell), a primary-secondary cell group cell (PSCell), and a secondary cell (SCell).

19. The method according to claim 16, wherein The rules further include a candidate set configured for self-scheduling and a candidate set configured for cross-carrier scheduling for the first cell respectively.

20. The method according to claim 19, wherein, The candidate set in the search space is configured for self-scheduling or cross-carrier scheduling.

21. An apparatus for wireless communication, the apparatus comprising a processor and a memory, the processor being configured to read instructions from the memory to perform the following operations: Transmit control information for a first cell according to a rule that the amount of blind detection resources for the first cell does not exceed the budget, where The budget includes a physical downlink control channel (PDCCH) candidate budget and a non-overlapping control channel element (CCE) budget, and wherein, when the first cell is scheduled by a primary scheduling cell and the first cell is also self-scheduled, the budget is determined by a terminal by counting only once for the first cell.

22. The apparatus according to claim 21, wherein the blind detection resources include a candidate set for blind detection of a physical downlink control channel (PDCCH) or the number of non-overlapping control channel elements (CCEs).

23. The apparatus according to claim 21, wherein the first cell includes one of a primary cell (PCell), a primary-secondary cell group cell (PSCell), and a secondary cell (SCell).

24. The device according to claim 21, wherein, The rules further include a candidate set configured for self-scheduling and a candidate set configured for cross-carrier scheduling for the first cell respectively.

25. The device according to claim 24, wherein, The candidate set in the search space is configured for self-scheduling or cross-carrier scheduling.

Images