Method and device for wireless communication and non-transitory computer readable medium

Abstract

The present application relates to a method, an apparatus, and a non-transitory computer readable medium having a code stored thereon for wireless communication. The method includes receiving, by a terminal, control information for a first cell on a master cell according to a rule that an amount of blind test resources for the first cell does not exceed a budget, the first cell being scheduled by the master cell and also being scheduled by itself.

Description

[0001] This application is a divisional application of the Chinese patent application with application number "202080098796.2", application date "May 14, 2020", and title "Resource Determination in Wireless Communications". Technical Field

[0002] This patent application is generally directed to wireless communications. Background Art

[0003] Mobile communications technology is driving the world towards an increasingly interconnected and networked society. Rapid growth and technological advancements in mobile communications are leading to greater demands for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectrum efficiency, and latency, are also crucial to meeting the demands of various communication scenarios. Various technologies are being explored, including new approaches to providing higher quality services. Summary of the Invention

[0004] The present application discloses methods, systems, and devices related to digital wireless communications, and more particularly, discloses techniques related to maintaining a PDCCH blind detection budget when a cell can be scheduled by another cell as well as itself.

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

[0006] In another exemplary aspect, a wireless communication device is disclosed that includes a processor configured to implement the methods described herein.

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

[0008] The details of one or more embodiments are set forth in the accompanying appended sections, the drawings, and the description that follows. Other features will become apparent from the description and drawings, and from the clauses. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A first example of CA scheduling is shown.

[0010] Figure 2 A second example of CA scheduling is described.

[0011] Figure 3 An example method for maintaining the PDCCH blind detection budget in the case where a cell may be scheduled by another cell as well as itself is shown.

[0012] Figure 4 An example of a wireless communication system is shown in which the technology according to one or more embodiments of the present technology can be applied.

[0013] Figure 5 A block diagram representation of a portion of a hardware platform. DETAILED DESCRIPTION

[0014] The development of the next generation of wireless communications—5G New Radio (NR)—is part of the ongoing mobile broadband evolution to meet growing network demands. NR will provide greater throughput, allowing more users to connect simultaneously. Other aspects, such as energy consumption, device cost, spectrum efficiency, and latency, are also important to meet the demands of various communication scenarios.

[0015] Fourth-generation mobile communication technology (4G), Long-Term Evolution (LTE) or LTE-Advanced (LTE-A), and fifth-generation mobile communication technology (5G) are facing increasing demand. Based on current development trends, 4G and 5G systems are developing support for enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). Furthermore, spectrum used for 4G can be reused in 5G through dynamic spectrum sharing (DSS).

[0016] In current 5G systems, an SCell can be the sole active or scheduled cell, while a PCell (or SCell) can include active cells and 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 does not change. The active cell is responsible for scheduling transmissions to and from the network over the wireless medium.

[0017] 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 physical uplink shared channel (PUSCH) on the PSCell, but the PDSCH or PUSCH on the P(S)Cell may not be scheduled by the PDCCH of the SCell. Taking into account the DSS in NR, the resources for the PDCCH of the PCell / SCell may be limited. In order to offload the PCell / SCell PDCCH, NR PDCCH enhancement for cross-carrier scheduling can be introduced, including the PDCCH scheduling of PDSCH or PUSCH by the SCell on the P(S)Cell. In particular, the total PDCCH blind detection budget can remain unchanged.

[0018] System Overview

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

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

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

[0022] 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 the search space, which are used for self-scheduling and also for cross-carrier scheduling. This may also include candidates configured in the search space being used for cross-carrier scheduling in addition to candidates configured for self-scheduling. This may also include candidates configured in the search space being used only for cross-carrier scheduling or for self-scheduling. In addition, all candidates for USS may include candidates for nrofCandidates (if any) and nrofCandidates-r17 (if any).

[0023] A third method may include configuring (or predefining) a blind detection order for a cell. The blind detection order may include first performing a self-scheduled blind detection, and then performing a cross-carrier scheduled blind detection. The order may also include first performing a cross-carrier scheduled blind detection, and then performing a self-scheduled blind detection. A cell may support both self-scheduling and cross-carrier scheduling.

[0024] A fourth method may include counting candidates for monitoring that are cross-carrier scheduled for the P(S)Cell in candidates for monitoring that are self-scheduling for the SCell.

[0025] In the case where P(S)Cell can be scheduled by SCell, maintaining the number of cells of P(S)Cell as 1 for both self-scheduling and cross-carrier scheduling includes one of the following methods. The first method may include PCell being counted as only one cell as the main cell for PCell or the scheduled cell for its main cell. The second method may include the PCell being counted as the P1 cell as the main cell for PCell, and the P2 cell as the scheduled cell for its main 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 a candidate for self-scheduling and M2 is a candidate for cross-carrier scheduling for the same cell. The second scheme may include configuring P1 and / or P2.

[0026] There can be two PDCCH blind detection parameters, one can include or while another may include or For each scheduled cell, the UE may not be required to monitor multiple DL bandwidths per time slot on the activated DL bandwidth part (BWP) with SCS configuration μ of the scheduling cell. PDCCH candidates or more The budget can be at least two parameters.

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

[0028]

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

[0030] Table 2 may provide the maximum number of non-overlapping CCEs in each slot for a single serving cell at a DL BWP with SCS configuration μ that a UE is expected to monitor for the corresponding PDCCH candidate set.

[0031] The CCEs of the PDCCH candidates may be non-overlapping if they correspond to different CORESET indices, or correspond to different first symbols for reception of the respective PDCCH candidates.

[0032]

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

[0034] If the UE is configured downlink cells, and the DL BWP has an SCS configuration μ, where For each scheduled cell, the UE may not be required to monitor more than PDCCH candidates or more non-overlapping CCEs.

[0035] If the UE is configured downlink cells, and the DL BWP has an SCS configuration μ, where The DL BWP of the activated cell is the activated DL BWP of the activated cell, and the DL BWP of the deactivated cell is the DL BWP with the index provided by the firstActiveDownlinkBWP-Id of the deactivated cell, then the UE may not be required to On one or more activated DL BWPs of one or more anchor cells of a downlink cell, more than PDCCH candidates or more non-overlapping CCEs.

[0036] For each scheduled cell, the UE may not be required to monitor more than PDCCH candidates or more non-overlapping CCEs.

[0037] For all search space sets in time slot n, S css Indicates that the cardinality is I css The CSS (Common Search Space) set is a collection of common search spaces, and the S uss Indicates the cardinality is J uss A collection of USS sets. j (0≤j<J uss ) in S uss The positions in can be sorted in ascending order according to the search space set index.

[0038] For CSS set S css (i), with Indicates the number of PDCCH candidates counted for monitoring, and for USS set S uss (j), with Indicates the number of PDCCH candidates counted for monitoring.

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

[0040] The UE may allocate PDCCH candidates for monitoring to the USS set for the primary cell with an activated DL BWP with SCS configuration μ in time slot n according to the following pseudo code. In the absence of allocated PDCCH candidates for monitoring, the UE may not desire to monitor the PDCCH in the USS set. This may indicate that all configured candidates in that USS are discarded.

[0041] V CCE (S uss (j)) represents the search space set S uss (j) is a set of non-overlapping CCEs, and c(V CCE (S uss (j))) indicates V CCE (Suss (j)) cardinality, where the allocated PDCCH candidates for monitoring can be considered for the CSS set and for all search space sets S uss (k)(0≤k≤j) of the PDCCH candidates allocated for monitoring, the search space set S is determined uss (j) Non-overlapping CCEs.

[0042]

[0043]

[0044] In the case where the P(S)Cell can be a scheduled cell (it can also be a master cell), the total PDCCH blind detection budget in each time slot can be greater than PDCCH candidates or more This may be because, for PDCCHs scheduled across carriers, the number of PDCCH candidates and the number of non-overlapping CCEs for monitoring can be counted separately in each time slot.

[0045] Although candidates are used as examples to represent PDCCH blind detection budgets in the following embodiments, similar non-overlapping CCEs may also be applied as described herein.

[0046] This embodiment described below may illustrate an embodiment for preventing an increase in the PDCCH blind detection budget when the P(S)Cell is a scheduled cell.

[0047] Example 1

[0048] If search space sharing for DL ​​(UL) is supported by the UE, at least one scheduled SCell with DCI format 0_1 / 1_1 of 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 scheduled SCell on the anchor cell, blind detection can be performed in the USS for the scheduled SCell.

[0049] In a carrier aggregation scenario, a P(S)Cell (named Cell A) is configured to be scheduled by an SCell (named Cell B). For Cell B, Cell B is configured to be the primary cell and support Primary Cell A. Cell A can be scheduled on Primary Cell B using CIF = X, where X can be a value in the set [1, ..., 7] or [0, ..., 7].

[0050] For PDCCH blind detection for P(S)Cell, this may include blind detection (BD) for the scheduling P(S)Cell itself when the P(S)Cell is the primary cell, and BD for the scheduling P(S)Cell when the primary cell is cell B. In order not to increase the PDCCH blind detection budget, the following solution may be used.

[0051] Cell A and other N serving cells scheduled by cell B may be configured, where N may include an integer greater than 0. Figure 1 is a block diagram 100 illustrating a first exemplary CA scheduling process. Figure 1 At least one of the active cells (N=2) (named cell C), CIF=Y is configured for cell C, and the size of DCI format 0_1 / 1_1 for active cell C can be the same as the size of DCI format 0_1 / 1_1 for active cell A. At the same time, the UE can support search space sharing by indicating via searchSpaceSharingCA-UL or via searchSpaceSharingCA-DL. For PDCCH blind detection of the scheduled PCell and scheduled SCell on the active 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 DCI format 0_2 or 1_2.

[0052] In some embodiments, the UE may support uplink search space sharing by indicating via searchSpaceSharingCA-UL.

[0053] For the main tuning 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 the main tuning cell A can be the same as the size of DCI format 0_1 ​​for the main tuning cell C. Then, for PDCCH blind detection for cell A and cell C on the main tuning cell, blind detection can only be performed in the USS determined by CIF=2 for cell C. In this way, using search space sharing, DCI with CIF=1 can also be detected in the USS determined by CIF=2. For cell A, PDCCH blind detection can also be performed when cell A is the main tuning cell. The total PDCCH blind detection budget may not increase.

[0054] In some embodiments, when the DCI size used to schedule SCells and the DCI size used to schedule P(S)Cells through search space sharing may be the same, blind detection is performed only in the USS for the scheduled SCell. Blind detection for P(S)Cells can be implemented by only including blind detection for P(S)Cells when the P(S)Cell is the primary cell, and excluding blind detection for P(S)Cells when the P(S)Cell is the scheduled cell. Therefore, when supporting P(S)Cell scheduling by SCells, the total PDCCH blind detection budget may not be increased. The complexity of blind detection for the UE may not be increased.

[0055] Example 2

[0056] A second embodiment may involve configuring M1 candidates for self-scheduling and M2 candidates for cross-carrier scheduling for the same cell. This configuration may 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; 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 candidates of nrofCandidates (if any) and nrofCandidates-r17 (if any).

[0057] In a carrier aggregation scenario, a P(S)Cell (named cell A) is configured to be scheduled by an SCell (named cell B). For cell B, cell B is configured to be the lead cell and to support lead cell A. Cell A can be scheduled on lead cell B using CIF = X, where X is a value from the set [1, ..., 7] or [0, ..., 7].

[0058] The PDCCH blind detection for the P(S)Cell includes BD for scheduling the P(S)Cell itself when the P(S)Cell is the primary cell, and BD for scheduling the P(S)Cell when the primary cell may be cell B. In order not to increase the PDCCH blind detection budget, the following scheme can be used.

[0059] For P(S)Cell, M1 candidates for self-scheduling and M2 candidates for cross-carrier scheduling for the same cell may be configured. The configuration method may 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 P(S)Cell, only nrofCandidates may 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 P(S)Cell, nrofCandidates may be configured for self-scheduling, and nrofCandidates-r17 may be configured for cross-carrier scheduling; the candidates configured in the search space are only used for cross-carrier scheduling (e.g., USS), for P(S)Cell, nrofCandidates may be configured for self-scheduling, or nrofCandidates-r17 may be configured for cross-carrier scheduling. In addition, when M1+M2=M, the candidates are in This may indicate that all candidates for the USS may include candidates from nrofCandidates (if any) and nrofCandidates-r17 (if any). After candidate discarding, the total PDCCH blind detection budget may not increase.

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

[0061]

[0062] In one embodiment, when scheduling of P(S)Cells by SCells is not supported, a common search space (CSS) #0 with 6 candidates (6 BDs), a CSS #1 with 6 candidates (6 BDs), and a USS (UE specific search space) #2 with 16 candidates (32 BDs) can be configured, for a total of 44 BDs. Meanwhile, the subcarrier spacing (SCS) includes 15 kHz for P(S)Cells, i.e., μ = 0. The candidates configured in the search space nrofCandidates can be used as candidate resources. The number of BDs, also known as candidates for monitoring, is obtained by multiplying the number of DCI formats of different sizes that can be carried by the candidates. For example, there may be only one size of DCI format in the CSS, so the number of BDs can be equal to the number of candidates. For example, there may be two sizes of DCI formats in the USS, so the number of BDs can be twice the number of candidates.

[0063] When the P(S)Cell supports scheduling 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. The BDs for self-scheduled USS#2 can include 32, and the BDs for cross-carrier scheduled USS#2 are 32, for a total of 76 BDs, which can exceed the PDCCH blind detection budget. To avoid exceeding the budget, one of the following methods can be used.

[0064] The first method may include that for USS#2, only nrofCandidates may be configured for both self-scheduling and cross-carrier scheduling for P(S)Cell. If the total number of candidates for nrofCandidates is 8 (i.e., 16 BDs), there may be 16 BDs for cross-carrier scheduling and 6+6+16=28 BDs for self-scheduling. The total BDs for P(S)Cell may be 44 BDs. For candidates discarded in time slots with all the above search spaces, the candidates for monitoring USS#2 may be 16+16=32, and under the assumption that μ=0 and In the case of , it may not be discarded. If the total number of candidates in nrofCandidates is 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 may be 52 BDs. For candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 may be 20+20=40, and under the assumption that μ=0 and can be discarded.

[0065] In the second method, for USS#2, the candidates configured in the search space can be used for cross-carrier scheduling in addition to the candidates configured for self-scheduling. If the total number of candidates of nrofCandidates is 6 (i.e., 12 BDs) and the total number of candidates of nrofCandidates-r17 is 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 BD 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 under the assumption that μ=0 and In the case of , it may not be discarded. If the total number of candidates of nrofCandidates is 8 (i.e., 16 BDs) and the total number of candidates of nrofCandidates-r17 is 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 may be 48 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 may be 16+20=36, and under the assumption that μ=0 and The case may not be discarded.

[0066] In the third method, for USS, the candidates configured in the search space can be used for self-scheduling or for being cross-carrier scheduled. 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, there may be 20 BDs for cross-carrier scheduling, and 6+6+12=24 BDs for self-scheduling. The total BD 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, and the candidates for monitoring USS#3 can be 20, assuming μ=0 and In this case, neither USS#2 nor USS#3 may be discarded. If the total number of candidates of nrofCandidates is 8 (i.e., 16 BDs) for self-scheduled USS#2 configuration, and the total number of candidates of nrofCandidates-r17 is 10 (i.e., 20 BDs) for cross-carrier scheduled USS#3 configuration, there may be 20 BDs for cross-carrier scheduling, and 8+6+16=28 BDs for self-scheduling. The total BD 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, and the candidates for monitoring USS#3 can be 20, then under the assumption that μ=0 and In this case, USS#2 may not be discarded, but USS#3 will be discarded. Therefore, USS#3 may not be used for cross-carrier scheduling of P(S)Cell, which may indicate that P(S)Cell scheduling by SCell through USS#3 may not be supported. If all candidates of nrofCandidates-r17 are 8 (i.e., 16 BDs) configured for cross-carrier scheduling of USS#2, and all candidates of nrofCandidates are 10 (i.e., 20 BDs) configured for self-scheduling of USS#3, there may be 16 BDs for cross-carrier scheduling, and 8+6+20=28 BDs for self-scheduling. The total BD for P(S)Cell may be 48 BDs. For the candidates discarded in the time slot with all the above search spaces, the candidates for monitoring USS#2 may be 16, and the candidates for monitoring USS#3 may be 20, then under the assumption that μ=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 P(S)Cell, which means that P(S)Cell can be scheduled by SCell through USS#2.

[0067] In one embodiment, 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, if there is at least one USS and the candidate configured in the USS for cross-carrier scheduling is a valid candidate for monitoring, the P(S)Cell can be scheduled by the SCell.

[0068] In one embodiment, the P(S)Cell supports both self-scheduling and cross-carrier scheduling by including valid USSs for cross-carrier scheduling for the P(S)Cell after candidate discarding in all configured search spaces. Therefore, when the P(S)Cell is supported to be scheduled by an SCell, the total PDCCH blind detection budget may not be increased. The UE's blind detection complexity may not be increased.

[0069] Example 3

[0070] A third embodiment may include predefining / configuring a blind detection order for a cell. The blind detection order may include first performing self-scheduling blind detection, then performing cross-carrier scheduled blind detection; or first performing cross-carrier scheduled blind detection, then performing self-scheduling blind detection. A cell may support both self-scheduling and cross-carrier scheduling.

[0071] In a carrier aggregation scenario, a P(S)Cell (named Cell A) is configured to be scheduled by an SCell (named Cell B). For Cell B, Cell B is configured to be the primary cell and support Primary Cell A. Cell A can be scheduled on Primary Cell B using CIF = X, where X can be a value in the set [1, ..., 7] or [0, ..., 7].

[0072] The PDCCH blind detection for the P(S)Cell includes BD for scheduling the P(S)Cell itself when the P(S)Cell is the primary cell, and BD for scheduling the P(S)Cell when the primary cell is cell B. To avoid increasing the PDCCH blind detection budget, the following scheme can be used.

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

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

[0075] Methods for configuring candidates for cross-carrier scheduling may include any of the following: candidates configured in the search space can be used for both self-scheduling and cross-carrier scheduling; candidates configured in the search space can be used for cross-carrier scheduling in addition to being configured for self-scheduling; candidates configured in the search space are used only for cross-carrier scheduling or self-scheduling. After candidates are discarded in the order of blind detection of the cell, the PDCCH blind detection complexity may not increase.

[0076] In one embodiment, when P(S)Cell is not supported for scheduling by 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, with a total of 44 BDs. At the same time, it is assumed that the subcarrier spacing (SCS) for P(S)Cell can be 15 khz, that is, μ=0. The number of BDs obtained by multiplying the number of nrofCandidates candidates that can be configured in the search space as candidate resources by the number of DCI formats of different sizes that can be carried by the candidates 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. 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.

[0077] If the P(S)Cell supports scheduling by the SCell, 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) are configured for self-scheduling. CSS#3 with 4 candidates (8 BDs) and CSS#4 with 4 candidates (8 BDs) are configured for cross-carrier scheduling (which implies scheduling by the SCell). The total number of BDs is 52, which exceeds the PDCCH blind detection budget. To avoid exceeding the budget, one of the following methods can be used.

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

[0079] In the second method, if the order of predefined / configured blind detection includes first performing cross-carrier scheduled blind detection and then performing self-scheduled blind detection, candidate discarding can be performed first on the USS configured for candidates to be cross-carrier scheduled. For candidate discarding in the time slot with all the above search spaces, the remaining part of the blind detection budget can be 44-(8+8)=28 (assuming μ=0 and) There may be no overbooking. The P(S)Cell may be scheduled by the SCell. The remaining portion of the blind detection budget may be used for candidate discarding of USSs configured as 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 may be supported to be scheduled by the SCell through 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 may be discarded and may not be used for self-scheduling of the P(S)Cell.

[0080] In one embodiment, if the order of predefined / configured blind detection includes first performing cross-carrier scheduled 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 expected that all candidates in all search spaces are larger 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, it may not be expected that all candidates for all CSSs and all search spaces with candidates for cross-carrier scheduling are larger 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 for self-scheduling, it may not be expected that all candidates for all CSSs and all search spaces with candidates for cross-carrier scheduling are larger than the PDCCH blind detection budget.

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

[0082] In one embodiment, the blind detection order is predefined / configured for cells within the constraints of the PDCCH blind detection budget to enable simultaneous support of self-scheduling and cross-carrier scheduling for P(S)Cells. This allows the total PDCCH blind detection budget to be maintained, even when the P(S)Cell is scheduled by an SCell. This also reduces the complexity of the UE's blind detection.

[0083] Example 4

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

[0085] The PDCCH blind detection for the P(S)Cell includes BD for scheduling the P(S)Cell itself when the P(S)Cell may include the main cell, and BD for scheduling the P(S)Cell when the main cell may be cell B. In order not to increase the PDCCH blind detection budget, the following scheme can be used.

[0086] For P(S)Cells, blind detection for P(S)Cells only includes blind detection for P(S)Cells when the P(S)Cell may be the scheduling cell. Blind detection for P(S)Cells when the P(S)Cell may be the scheduled cell is counted as a candidate for monitoring (also called blind detection) for self-scheduling of SCells. P(S)Cells may be scheduled by SCells.

[0087] Candidate overbooking / dropping can only be performed on the primary cell. The total number of candidates for monitoring an SCell may not exceed the PDCCH blind detection budget. Consequently, it is undesirable that the number of candidates for monitoring a P(S)Cell that is cross-carrier scheduled and the number of candidates for monitoring a SCell that is self-scheduled exceed the PDCCH blind detection budget.

[0088] In one embodiment, when P(S)Cell is not supported for scheduling by 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. At the same time, it is assumed that the subcarrier spacing (SCS) for P(S)Cell is 15 kHz, that is, μ=0. The number of BDs obtained by multiplying the number of nrofCandidates candidates that can be configured in the search space as candidate resources by the number of DCI formats of different sizes that can be carried by the candidates is also called candidates for monitoring. For example, there can be only one size of DCI format in the CSS, so the number of BDs is equal to the number of candidates. For example, there can be two sizes of DCI formats in the USS, so the number of BDs is twice the number of candidates.

[0089] If the P(S)Cell supports scheduling 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 number of BDs can be 52, which may exceed the PDCCH blind detection budget. To avoid exceeding the budget, the following method can be used.

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

[0091] In one embodiment, candidates for monitoring for cross-carrier scheduling of P(S)Cells are counted among candidates for monitoring for SCell self-scheduling, and the sum of candidates for monitoring for cross-carrier scheduling of P(S)Cells and candidates for monitoring for self-scheduling of SCells is guaranteed to be no greater than the PDCCH blind detection budget configured by the gNB. This supports both P(S)Cell self-scheduling and cross-carrier scheduling. When P(S)Cells are supported for SCell scheduling, the total PDCCH blind detection budget may not increase, and the UE's blind detection complexity may not increase.

[0092] Example 5

[0093] When a P(S)Cell can be scheduled by an SCell, the number of cells in the P(S)Cell is 1 for both self-scheduling and cross-carrier scheduling. In a carrier aggregation (CA) scenario, a P(S)Cell (named cell A) can be scheduled by an SCell (named cell B). For cell B, it is configured that cell B can be the lead cell and support lead cell A. It can be assumed that cell A is scheduled on lead cell B using CIF = X, where X is a value from the set [1, ..., 7] or [0, ..., 7].

[0094] Figure 2 A block diagram 200 of a second example CA scheduling process is shown. The cells may be configured such that cell 2 schedules cells 1 to 6, where cell 1 may be a PCell with μ = 0 and may be scheduled by cell 2 with μ = 1. Cells 2 to 6 are SCells. The UE may report its carrier aggregation capability as pdcch-BlindDetectionCA = 4 cells, which means Because the 6 configured cells may be larger than So CA scaling is expected. This may indicate that the UE does not need to One or more downlink cells and one or more activated DL BWPs of the main cells monitor more than PDCCH candidates.

[0095] In some cases, M_total_15 kHz = floor(4*44*1 / 6) = 29; M_total_30 kHz = floor(4*36*6 / 6) = 144. As a result, because 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 PCell does not support scheduling. In the case where the PCell does not support scheduling, M_total_15 kHz = floor(4*44*1 / 6) = 29; M_total_30 kHz = floor(4*36*5 / 6) = 120.

[0096] In one embodiment, when a P(S)Cell can be scheduled by an SCell, maintaining the number of cells of the P(S)Cell as 1 for both self-scheduling and cross-carrier scheduling may include one of the following methods.

[0097] The first method may include the PCell as the primary cell for the PCell, or the scheduled cell for its primary cell is counted as only one cell. For example, the PCell may be counted as only one cell as the primary cell for the PCell, then M_total_15 kHz = floor(4*44*1 / 6) = 29; M_total_30 kHz = floor(4*36*5 / 6) = 120. The blind detection complexity may not increase. The PDCCH blind detection budget may not increase.

[0098] In the second method, the PCell is counted as the P1 cell as the main cell for the PCell, and the P2 cell as the scheduled cell for its main cell. In some cases, P1+P2=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 a candidate for self-scheduling and M2 is a candidate for cross-carrier scheduling for the same cell. For example, M1=22, M2=22, then P1=0.5, P2=0.5. Therefore, 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, configuring P1=0.6, P2=0.4. Therefore, in this example, M_total_15khz = floor(4*44*0.6 / 6) = 17; M_total_30khz = floor(4*36*5.4 / 6) = 129. Blind detection may not increase. PDCCH blind detection budget may not increase.

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

[0100] Figure 3An example method 300 is shown for maintaining a PDCCH blind detection budget when a cell can be scheduled by another cell as well as itself. The method may include receiving, by a terminal on a lead cell, control information for a first cell scheduled by the lead cell and also scheduled by itself, according to a rule that an amount of blind detection resources for the first cell does not exceed the budget (block 302). The first cell may include a candidate cell to be scheduled by the lead cell. The rule may specify that the PDCCH blind detection resources remain unchanged.

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

[0102] 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).

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

[0104] In some embodiments, the method includes performing a blind detection process on the first cell on an anchor cell, the anchor cell only including a search space of the second cell.

[0105] In some embodiments, the rule further includes: configuring, for the first cell, a plurality of candidates for self-scheduling and a plurality of candidates for cross-carrier scheduling.

[0106] In some embodiments, multiple candidates in the search space are configured for both self-scheduling and for being cross-carrier scheduled.

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

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

[0109] In some embodiments, the number of Physical Downlink Control Channel (PDCCH) candidates counted for monitoring the search space includes candidates for self-scheduling combined with candidates for cross-carrier scheduling.

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

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

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

[0113] In some embodiments, the order includes first performing the cross-carrier scheduled blind detection process, followed by performing the self-scheduled blind detection process.

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

[0115] In some embodiments, the rule further includes: counting candidates for monitoring of the first cell that is scheduled across carriers into a plurality of candidates for monitoring of the main cell.

[0116] In some embodiments, the sum of the number of candidates for monitoring of the first cell scheduled across carriers and the number of candidates for monitoring of the tuning cell is not greater than a budget.

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

[0118] In some embodiments, the number of cells used for the first cell is counted as one cell that is a scheduling cell for the first cell or a scheduled cell for the scheduling cell.

[0119] In some embodiments, counting the number of cells of the first cell as 1 cell includes: counting the first cell as a P1 cell serving as a main cell for the first cell, and counting the P2 cell as a scheduled cell for the main cell, wherein the number of cells of P1 and the number of cells of P2 combined equal 1.

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

[0121] Example Wireless System

[0122] Figure 4An example of a wireless communication system in which techniques according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 400 may include one or more base stations (BSs) 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 stations may implement the functionality of a prime cell or a candidate cell, as described herein.

[0123] The core network 425 can communicate with one or more base stations 405a and 405b. The core network 425 provides connectivity to other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to 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, base stations 405a and 405b may be quasi-co-located or separately installed on-site. The wireless devices 410a, 410b, 410c, and 410d may support a variety of different radio access technologies.

[0124] In some embodiments, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that can be used to connect to different wireless networks.

[0125] Figure 5 5 is a block diagram representation of a portion of a hardware platform. A hardware platform 505, such as a network device or base station or wireless device (or UE), may include a processor electronics 510, 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 send 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 portion of the transceiver electronics 515. In some embodiments, the hardware platform 505 is used to implement at least some of the disclosed techniques, modules, or functions.

[0126] in conclusion

[0127] From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for illustrative purposes, but that various modifications may be made without departing from the scope of the invention. Accordingly, the presently disclosed technology is not limited, except as limited by the appended claims.

[0128] The disclosed and other embodiments, modules, and functional operations described in this application can be implemented in digital electronic circuit systems, 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 these. 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 a data processing apparatus or for controlling the operation of the 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 that implements a machine-readable propagated signal, or a combination of one or more of these. The term "data processing apparatus" encompasses all devices, equipment, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus can include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these. A propagated signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to a suitable receiver device.

[0129] 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. A program may be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files that store one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communications network.

[0130] The processes and logic flows described herein may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may be implemented as, special purpose logic circuitry, for example, an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0131] By way of example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. Generally, a processor will receive instructions and data from read-only memory or 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 (e.g., magnetic, magneto-optical, 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 storage devices, including, by way of example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated into, dedicated logic circuitry.

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

[0133] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that the operations be performed in the particular order shown, or in sequential order, or that all illustrated operations be performed, to achieve the desired results. Furthermore, the separation of various system components in the embodiments described in this patent application should not be understood as requiring such separation in all embodiments.

[0134] Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this patent document.

Claims

1. A method for wireless communication, comprising: The terminal receives control information for the first cell on the anchor cell according to a rule that an amount of blind detection resources for the first cell does not exceed a budget, wherein the first cell is scheduled by the anchor cell and the first cell is also scheduled by itself. 2 . The method according to claim 1 , wherein the blind detection resource comprises the number of candidates 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 comprises one of a primary cell (PCell), a primary-secondary cell group cell (PSCell), and a secondary cell (SCell).

4. The method according to claim 1, wherein The rule further includes: a second cell different from the first cell includes the same downlink control information DCI format of the first cell having the same size, wherein the terminal reports a capability of supporting search space sharing for downlink and / or uplink.

5. The method according to claim 4, further comprising: A blind detection process is performed on the first cell on the anchor cell, and the blind detection process is only included in the search space of the second cell.

6. The method according to claim 1, wherein The rule further includes: configuring, for the first cell, the number of candidate sets for self-scheduling and the number of candidate sets for cross-carrier scheduling.

7. The method according to claim 6, wherein: The multiple candidates in the search space are configured for both self-scheduling and cross-carrier scheduling.

8. The method according to claim 6, wherein: The plurality of candidates in the search space are configured for self-scheduling and for being cross-carrier scheduled, respectively.

9. An apparatus for wireless communication, the apparatus comprising a processor configured to perform the method according to any one of claims 1 to 8.

10. A non-transitory computer-readable medium having stored thereon code, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 8.

Images