A method, device, equipment and storage medium for configuring a scheduling primary cell

Abstract

The present application proposes a method, device, equipment and storage medium for scheduling a primary cell, which includes: configuring cross-carrier scheduling configuration information of carriers so that the primary cell supports self-scheduling and being scheduled. The function of scheduling the primary cell by the secondary cell can reduce the demand for control resources of the primary cell.

Description

Technical Field

[0001] The present application relates to a wireless communication network, and in particular to a method, device, equipment and storage medium for scheduling a primary cell. Background Art

[0002] In the current 5G communication system, the primary cell PCell can schedule the secondary cell SCell, but the SCell cannot schedule the PCell. When considering the dynamic spectrum sharing (DSS) between the 5G system and the 4G system, the PDCCH resources on the PCell using DSS in the 5G system are limited due to the small bandwidth of the 4G system and the need to avoid interference from the 4G system's PDCCH (Physical Downlink Control Channel) and CRS (Cell Reference Signal). Summary of the invention

[0003] The present application provides a method, apparatus, device and storage medium for configuring a scheduling primary cell, which enables the primary cell to support self-scheduling and being scheduled.

[0004] The embodiment of the present application provides a method for configuring a scheduling primary cell, including:

[0005] The cross-carrier scheduling configuration information of the carrier is configured so that the primary cell supports self-scheduling and being scheduled.

[0006] An embodiment of the present application provides a configuration device for scheduling a primary cell, including:

[0007] The cross-carrier scheduling configuration module is configured to configure the cross-carrier scheduling configuration information of the carrier so that the primary cell supports self-scheduling and being scheduled.

[0008] An embodiment of the present application provides a device, including: a memory, and one or more processors;

[0009] The memory is used to store one or more programs;

[0010] When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the methods in the embodiments of the present application.

[0011] An embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.

[0012] The embodiment of the present application configures the cross-carrier scheduling configuration information of the carrier so that the primary cell supports self-scheduling and being scheduled, realizes the function of the secondary cell scheduling the primary cell, and can reduce the demand for control resources of the primary cell.

[0013] With regard to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a flowchart of a method for configuring a scheduling primary cell in an embodiment of the present application;

[0015] Figure 2 A schematic diagram of the structure of a configuration device for scheduling a primary cell in an embodiment of the present application;

[0016] Figure 3 This is a schematic diagram of the structure of a device in an embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solution and advantages of the present application more clear, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0018] At present, the 4th Generation mobile communication technology (4G), Long-Term Evolution (LTE) / Long-Term Evolution Advance (LTE-Advance / LTE-A) and the 5th Generation mobile communication technology (5G) are facing more and more demands. From the current development trend, both 4G and 5G systems are studying the features that support enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission, and massive connections. And the 5G system also allows the reuse of 4G spectrum through DSS.

[0019] In the existing 5G system and standards, RRC configures the carrier for self-scheduling or being scheduled. Self-scheduling means receiving downlink control information (DCI) on the current carrier and scheduling the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) on the current carrier. Being scheduled means receiving DCI on another carrier and scheduling the PDSCH or PUSCH on the carrier. When RRC configures a carrier (denoted as carrier C) to be scheduled, RRC needs to configure the scheduling carrier index of carrier C (that is, which carrier schedules carrier C) and configure the CIF value of carrier C in the scheduling carrier. When the CIF field in the DCI on the main carrier indicates the CIF value of carrier C in the scheduling carrier, the DCI schedules PDSCH or PUSCH on carrier C. Cross-carrier scheduling is configured by the RRC cross-carrier scheduling configuration information CrossCarrierSchedulingConfig. The schedulingCellId in the CrossCarrierSchedulingConfig information element configures the scheduling carrier index, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig information element configures the CIF value of the carrier in the scheduling carrier. Assuming that RRC configures carrier C to be cross-carrier scheduled by carrier A and configures the CIF value of carrier C in the scheduling carrier to be 1, when the CIF value indicated by the CIF field of the DCI on carrier A is 1, this DCI schedules PDSCH or PUSCH on carrier C. It should be noted that the CIF field cannot be configured in DCI formats 1_0 and 0_0 (also called fallback downlink control information fallback DCI), so DCI formats 1_0 and 0_0 can only be used for self-scheduling but not for cross-carrier scheduling; the CIF field can be configured in DCI format 0_1, DCI format 0_2, DCI format 1_1 and DCI format 1_2 (also called non-fallback downlink control information non-fallback DCI), and they can be used for cross-carrier scheduling.

[0020] When RRC configures the carrier as self-scheduled, DCI format 1_0 can only be used to schedule PDSCH on this carrier, DCI format 0_0 can only be used to schedule PUSCH on this carrier, DCI format 1_1 and CIF = 0 and DCI format 1_2 and CIF = 0 are used to schedule PDSCH on this carrier, DCI format 0_1 ​​and CIF = 0 and DCI format 0_2 and CIF = 0 are used to schedule PUSCH on this carrier. When RRC configures the carrier as scheduled, the CIF field of the DCI (DCI format 0_1, DCI format 0_2, DCI format 1_1 and DCI format 1_2) on the scheduling carrier indicates that the CIF value configured for the carrier in the scheduling carrier indicates cross-carrier scheduling of the carrier, and one CIF value can only correspond to one carrier. Currently, a carrier can only be configured as self-scheduled or scheduled, and cannot be configured as self-scheduled and scheduled at the same time. Currently, the primary cell can only be configured for self-scheduling, which results in limited PDCCH capacity in DSS and a high load on transmission control signaling in the 5G system.

[0021] Since the primary cells (PCells) seen by different user equipments (UEs) may be different, and each carrier of different UEs is independently configured, the PCell described in the embodiment of the present application represents a PCell for one terminal.

[0022] In the description of PCell in the embodiment of the present application, when the secondary cell group (SCG) is configured, the primary secondary cell (PSCell) uses the same processing method as the PCell described in the embodiment of the present application. Therefore, it can be understood that the cross-carrier scheduling configuration information configuration method of the primary cell described in the embodiment of the present application is applicable to both PCell and PSCell.

[0023] When RRC configures a carrier (denoted as carrier B) for self-scheduling, RRC will configure carrier B scheduling cell information schedulingCellInfo as own when configuring CrossCarrierSchedulingConfig, that is, self-scheduling. Furthermore, whether there is a CIF field in the non-fallback DCI is configured through cif-Presence. When configured to true, there is a CIF bit field, and CIF=0 indicates self-scheduling, that is, scheduling carrier B, and scheduling other CIF values ​​indicates scheduling other carriers; when configured to false, there is no CIF field, and only self-scheduling is possible.

[0024] When RRC configures a carrier (denoted as carrier C) to be scheduled, RRC will configure the scheduling cell information schedulingCellInfo of carrier C to other when configuring CrossCarrierSchedulingConfig, that is, it is scheduled. Furthermore, the scheduling carrier index of carrier A that schedules carrier C is configured, that is, the scheduling carrier index of carrier A is determined by configuring the ServCellIndex corresponding to schedulingCellId, where ServCellIndex of PCell = 0, and the scheduling carrier indexes of other cells are also configured by high-level signaling; the CIF value of carrier C in the scheduling carrier is configured, and the CIF value cif-InSchedulingCell is a positive integer from 1 to 7. Assuming that RRC configures carrier C to be cross-carrier scheduled by carrier A and configures the CIF value of carrier C in the scheduling carrier to be 1, when the CIF field of the DCI on carrier A indicates that the CIF index is 1, then this DCI schedules PDSCH or PUSCH on carrier C.

[0025] In the prior art, only the scheduling cell information of the carrier of the SCell can be configured as other; for a carrier other than the PCell, the scheduling cell information can be configured as own or other.

[0026] In the embodiment of the present application, Figure 1 A flowchart of a method for scheduling a primary cell is shown, the method comprising:

[0027] S110. Configure cross-carrier scheduling configuration information of the carrier so that the primary cell supports self-scheduling and being scheduled.

[0028] Among them, in the prior art, the scheduling cell information of the primary cell can only be configured as own, that is, self-scheduling. Then, if you want to realize that the primary cell supports self-scheduling and being scheduled, you can configure the cross-carrier scheduling configuration information of the primary cell carrier so that the primary cell can be configured to be scheduled on the basis of originally supporting self-scheduling; you can also configure the cross-carrier scheduling configuration information of the secondary cell carrier so that the primary cell can be scheduled by the secondary cell.

[0029] In one implementation, when the carrier is a primary cell, the scheduling cell information of the primary cell is configured to be scheduled; and the scheduling carrier index of the primary cell is configured and the carrier indication field CIF value of the primary cell in the scheduling carrier is configured.

[0030] In the carrier aggregation (CA) scenario, when performing RRC configuration CrossCarrierSchedulingConfig for PCell (denoted as carrier C, whose scheduling carrier index ServCellIndex = 0), the scheduling cell information schedulingCellInfo of carrier C is configured as other, that is, it is scheduled. At this time, the scheduling carrier index of carrier A (called the main scheduling carrier) of scheduling carrier C (called the scheduled carrier) is further configured. At this time, carrier A is SCell, that is, the scheduling carrier index of carrier A is determined by configuring the ServCellIndex corresponding to schedulingCellId, and the ServCellIndex of carrier A>0, which can be selected as an integer between 1 and 31, for example, ServCellIndex = 3; configure the CIF value of carrier C in the scheduling carrier, and the CIF value cif-InSchedulingCell can be selected as a positive integer from 1 to 7, for example, CIF = 1.

[0031] At this time, further, the main cell also has a self-scheduling function. Optionally, the main cell also has self-scheduling capability, including: the main cell has self-scheduling capability and the CIF domain does not exist; or the main cell has self-scheduling capability and whether the CIF domain exists is configured through high-level signaling.

[0032] For SCell (called carrier A, whose cell index ServCellIndex>0), for example, the carrier with ServCellIndex=3 is carrier A. When RRC configures CrossCarrierSchedulingConfig, the scheduling cell information schedulingCellInfo of carrier A is configured as own, that is, self-scheduling. Further, the cif-Presence of carrier A is configured as true, and the CIF bit domain exists.

[0033] Further, the number of scheduled carrier indices of the primary cell is configured as a preset number, wherein the preset number may be a positive integer such as 1, 2, or 3. In this way, the number of SCells that schedule PCells is limited, and preferably, the preset number is 1, that is, only one SCell is supported to schedule PCell.

[0034] In summary, in this implementation, SCell schedules PCell, and PCell also has a self-scheduling function.

[0035] Through this implementation method, the basic structure of the current CrossCarrierSchedulingConfig configuration is not changed. Only when schedulingCellInfo is configured for PCell, it can be configured as other. And when PCell is configured as other, it is assumed that PCell also has self-scheduling function. At this time, when PCell is self-scheduled, there is no CIF domain or there is CIF and CIF=0 means scheduling PCell; when scheduled across carriers by SCell, the DCI of the corresponding PCell is received according to the configured CIF value (for example, when CIF=1). At this time, the CrossCarrierSchedulingConfig configuration for SCell does not need to be modified. When scheduling PCell, schedulingCellInfo needs to be configured as self-scheduling own.

[0036] The configuration method for scheduling the main cell provided by this implementation mode realizes the function of scheduling the main cell by the secondary cell by extending the configuration of the main cell as a scheduled carrier and assuming that the main cell has a self-scheduling function. This can reduce the demand for control resources of the main cell, better share the control overhead of the main cell through the dynamic load of the secondary cell, and improve the scheduling flexibility of the 5G system when reusing the 4G spectrum.

[0037] In one implementation, when the carrier is a primary cell, the scheduling cell information of the primary cell is configured as self-scheduling and scheduled; and whether the primary cell has a CIF is configured, the scheduling carrier index of the primary cell is configured, and the CIF value of the primary cell in the scheduling carrier is configured.

[0038] In the CA scenario, when performing RRC configuration CrossCarrierSchedulingConfig for PCell (called carrier C, whose cell index ServCellIndex = 0), the scheduling cell information schedulingCellInfo of carrier C is configured as ownand other, that is, self-scheduling and scheduling are supported at the same time, that is, a new option is added to schedulingCellInfo, which is own and other. At this time, the existence of the CIF domain of carrier C (called the scheduled carrier) (cif-Presence), the scheduling carrier index (schedulingCellId) and the CIF value (cif-InSchedulingCell) are further configured. The CIF value is the CIF value of the main carrier SCell (called carrier A) when scheduling carrier C. For example: cif-Presence is configured to false. At this time, carrier C does not support the CIF domain, that is, carrier C does not support being scheduled; the scheduling carrier index of the scheduled carrier A (called the main carrier) is configured. At this time, carrier A is SCell, that is, the scheduling carrier index of carrier A is determined by configuring the ServCellIndex corresponding to the schedulingCellId, and the ServCellIndex of carrier A>0, which can be selected as an integer between 1 and 31, for example, ServCellIndex=2; the CIF value (cif-InSchedulingCell) is configured as an integer between 1 and 7, for example, CIF=3.

[0039] For example, the CrossCarrierSchedulingConfig element is modified as follows:

[0040]

[0041]

[0042] Furthermore, there are restrictions on the self-scheduling function of PCell. Optionally, the self-scheduling DCI sent on PCell does not have a CIF field. That is, in the own and other option, cif-Presence does not exist, or Presence is always configured as false.

[0043] Furthermore, the newly added own and other option in schedulingCellInfo is limited to Pcell configuration only, that is, it can be configured for the carrier with the scheduling carrier index ServCellIndex of 0, and it cannot be configured for ServCellIndex>0. Or it can only be limited to Pcell or PSCell configuration, where ServCellIndex=0 is PCell, and ServCellIndex of PSCell is a configurable value, which can be selected as an integer between 1 and 31.

[0044] For SCell (called carrier A, whose cell index ServCellIndex>0), for example, the carrier with ServCellIndex=3 is carrier A. When RRC configures CrossCarrierSchedulingConfig, the scheduling cell information schedulingCellInfo of carrier A is configured as own, that is, self-scheduling. Further, cif-Presence is configured as true, and the CIF bit field exists.

[0045] Further, the number of scheduled carrier indices of the primary cell is configured as a preset number, wherein the preset number may be a positive integer such as 1, 2, or 3. In this way, the number of SCells that schedule PCells is limited, and preferably, the preset number is 1, that is, only one SCell is supported to schedule PCell.

[0046] In summary, in this implementation, SCell schedules PCell, and PCell also has a self-scheduling function.

[0047] Through this embodiment, an option is added to the scheduling cell information schedulingCellInfo in the basic structure of the current CrossCarrierSchedulingConfig configuration, namely, self-scheduling and being scheduled own and other. At this time, when self-scheduling, there is no CIF field or there is CIF and CIF=0 indicates scheduling PCell; when being cross-carrier scheduled by SCell, the DCI of the corresponding SCell is received according to the configured CIF value in the scheduling carrier (for example, when CIF=1). At this time, the CrossCarrierSchedulingConfig configuration for SCell does not need to be modified. When scheduling PCell, schedulingCellInfo needs to be configured as self-scheduling own.

[0048] The configuration method for scheduling the main cell provided by this implementation mode realizes the function of scheduling the main cell by the secondary cell by extending the configuration of the main cell to add the configuration as the scheduled carrier during self-scheduling, which can reduce the demand for the control resources of the main cell, better share the control overhead of the main cell through the dynamic load of the secondary cell, and improve the scheduling flexibility of the 5G system when reusing the 4G spectrum.

[0049] In one implementation, when the carrier is a primary cell, the scheduling cell information of the primary cell is configured as self-scheduling; and whether the primary cell is allowed to be scheduled is configured. When scheduling is allowed, the scheduling carrier index of the primary cell is configured and the CIF value of the primary cell in the scheduling carrier is configured.

[0050] In the CA scenario, when performing RRC configuration CrossCarrierSchedulingConfig for PCell (called carrier C, whose cell index ServCellIndex = 0), the scheduling cell information schedulingCellInfo of carrier C is configured as own, indicating self-scheduling. Further, whether SCell is allowed to schedule PCell is configured. If allowed, the scheduling carrier index of the SCell and the CIF value of the SCell scheduling PCell are configured, for example, ServCellIndex of the SCell is configured as 3 and CIF of the SCell scheduling PCell is configured as 1.

[0051] Optionally, configuring whether the primary cell is allowed to be scheduled includes: configuring whether the primary cell is allowed to be scheduled or not by displaying; or determining whether the primary cell is allowed to be scheduled or not by preset rules.

[0052] Regarding whether the primary cell is allowed or not to be scheduled by display configuration, in an exemplary implementation, first configure whether to allow SCell to schedule PCell. Secondly, when SCell is not allowed to schedule PCell, there is no need to configure the scheduling carrier index of the SCell and the CIF value of SCell scheduling PCell; when PCell scheduling is allowed, it is necessary to configure the scheduling carrier index of the SCell and the CIF value of SCell scheduling PCell.

[0053] For determining whether the primary cell is allowed or not to be scheduled by a preset rule, the preset rule includes at least one of the following: when the CIF value of the primary cell in the scheduling carrier is configured, it indicates that the primary cell is allowed to be scheduled, and when the CIF value of the primary cell in the scheduling carrier is not configured, it indicates that the primary cell is not allowed to be scheduled; when the scheduling carrier index of the primary cell is configured, it indicates that the primary cell is allowed to be scheduled, and when the scheduling carrier index of the primary cell is not configured, it indicates that the primary cell is not allowed to be scheduled. In an exemplary implementation, only the SCell scheduling carrier index for scheduling PCell and the CIF value for SCell scheduling PCell are configured. A further method for indicating whether scheduling PCell is allowed is one of the following: (1) when the CIF value is configured, such as an integer between 1 and 7, it indicates that scheduling PCell is allowed, and when the CIF value is not configured, it indicates that scheduling PCell is not allowed; (2) when the SCell index for scheduling PCell is configured, such as an integer between 1 and 31, it indicates that scheduling PCell is allowed, and when the SCell index for scheduling PCell is not configured, it indicates that scheduling PCell is not allowed.

[0054] For example, the CrossCarrierSchedulingConfig information element is modified as follows: add the SCell scheduling carrier index for scheduling PCell and the CIF value of PCell when the SCell schedules PCell. When the SCell scheduling carrier index for scheduling PCell and the CIF value of PCell are configured, that is, when schedulingSCellId is configured as an integer between 1-31 (that is, at this time, the configurable value ServCellIndex of schedulingSCellId is an integer between 1-31), and cif-InSchedulingSCellforPCell is an integer between 1-7, it means that scheduling PCell is allowed; when the SCell scheduling carrier index for scheduling PCell and the CIF value of PCell are not configured, that is, schedulingSCellId and cif-InSchedulingSCellforPCell are not configured, it means that scheduling PCell is not allowed. At this time, schedulingSCellId and cif-InSchedulingSCellforPCell are optional.

[0055]

[0056]

[0057] Further preset rules include at least one of the following: when the configured CIF value of the primary cell in the scheduling carrier is an element in the value set X, it indicates that the primary cell is allowed to be scheduled; when the configured CIF value of the primary cell in the scheduling carrier is Y and Y is not equal to any element in the value set X, it indicates that the primary cell is not allowed to be scheduled; when the configured scheduling carrier index value of the primary cell is an element in the value set M, it indicates that the primary cell is allowed to be scheduled; when the configured scheduling carrier index value of the primary cell is N and N is not equal to any element in the value set M, it indicates that the primary cell is not allowed to be scheduled. Among them, the elements in the value set X are integers greater than 0, preferably integers from 1 to 7, and Y is preferably 0. The elements in the value set M are integers greater than 0, preferably integers from 1 to 31, and N is preferably 0. In an exemplary implementation, the method for indicating whether PCell scheduling is allowed is one of the following: (1) when a CIF value is configured, such as an integer between 1 and 7, it indicates that PCell scheduling is allowed; when the CIF value is configured to be 0, it indicates that PCell scheduling is not allowed; (2) when an SCell scheduling carrier index for scheduling PCell is configured, such as an integer between 1 and 31, it indicates that PCell scheduling is allowed; when the SCell index for scheduling PCell is configured to be 0, it indicates that PCell scheduling is not allowed.

[0058] For example, the CrossCarrierSchedulingConfig information element is modified as follows: add the SCell scheduling carrier index of the PCell and the CIF value of the PCell when the SCell schedules the PCell. When the SCell scheduling carrier index and the CIF value of the PCell are configured, that is, when the schedulingSCellId is configured as an integer between 1-31, and cif-InSchedulingSCellforPCell is an integer between 1-7, it means that the PCell is allowed to be scheduled; when the SCell index schedulingSCellId of the PCell is configured to be 0, and / or the CIF value of the PCell is 0, that is, the schedulingSCellId is configured to be 0, and / or the cif-InSchedulingCellforPCell is 0, it means that the PCell is not allowed to be scheduled. Because the CIF value of 0 is used for the self-scheduling of the SCell, that is, when there is a CIF field, CIF=0 indicates that the SCell itself; the schedulingSCellId value of 0 is the PCell.

[0059]

[0060]

[0061] Furthermore, cif-Presence is configured as true (CIF field exists) or false (CIF field does not exist), indicating whether there is a CIF bit field. Furthermore, there are restrictions on the self-scheduling function of PCell. Optionally, the self-scheduling DCI sent on PCell does not have a CIF field. When configured as own, cif-Presence does not exist, or Presence is always configured as false.

[0062] For SCell (called carrier A, whose cell index ServCellIndex>0), for example, the carrier with ServCellIndex=3 is carrier A. When RRC configures CrossCarrierSchedulingConfig, the scheduling cell information schedulingCellInfo of carrier A is configured as own, that is, self-scheduling. Further, cif-Presence is configured as true, and the CIF bit field exists.

[0063] Further, the number of scheduled carrier indices of the primary cell is configured as a preset number, wherein the preset number may be a positive integer such as 1, 2, or 3. In this way, the number of SCells that schedule PCells is limited, and preferably, the preset number is 1, that is, only one SCell is supported to schedule PCell.

[0064] In summary, in this implementation, SCell schedules PCell, and PCell also has a self-scheduling function.

[0065] Through this implementation, when the scheduling cell information schedulingCellInfo in the basic structure of the current CrossCarrierSchedulingConfig configuration is configured as self-scheduling own, the SCell scheduling carrier index of the PCell and the CIF value when scheduling the PCell are added. At this time, when the PCell is self-scheduled, there is no CIF field or there is CIF and CIF=0 indicates that the PCell is scheduled; when cross-carrier scheduled by the SCell, the DCI of the corresponding SCell is received according to the configured CIF value (for example, when CIF=1). At this time, the CrossCarrierSchedulingConfig configuration for the SCell does not need to be modified. When scheduling the PCell, schedulingCellInfo needs to be configured as self-scheduling own.

[0066] The configuration method for scheduling the main cell provided by this implementation mode realizes the function of scheduling the main cell by the secondary cell by extending the configuration of the main cell as a modulated carrier and a main modulating carrier, which can reduce the demand for control resources of the main cell, better share the control overhead of the main cell through the dynamic load of the secondary cell, and improve the scheduling flexibility of the 5G system when reusing the 4G spectrum.

[0067] In one implementation, when the carrier is a secondary cell, the scheduling cell information of the secondary cell is configured as self-scheduling; and whether the secondary cell is allowed to schedule the primary cell is configured, and when scheduling the primary cell is allowed, the CIF value of the primary cell in the secondary cell is configured.

[0068] Optionally, the configuring whether the secondary cell is allowed to schedule the primary cell includes: explicitly configuring whether the secondary cell is allowed or not to schedule the primary cell; or determining whether the secondary cell is allowed or not to schedule the primary cell through a preset rule.

[0069] The preset rule includes: when the CIF value of the primary cell in the secondary cell is configured, it indicates that the primary cell is allowed to be scheduled; when the CIF value of the primary cell in the secondary cell is not configured, it indicates that the primary cell is not allowed to be scheduled; or when the configured CIF value of the primary cell in the secondary cell is an element in the value set X, it indicates that the primary cell is allowed to be scheduled; when the configured CIF value of the primary cell in the secondary cell is Y and Y is not equal to any element in the value set X, it indicates that the primary cell is not allowed to be scheduled. The elements in the value set X are integers greater than 0, preferably integers from 1 to 7.

[0070] In the CA scenario, when performing RRC configuration CrossCarrierSchedulingConfig for PCell (called carrier C, whose cell index ServCellIndex = 0), the scheduling cell information schedulingCellInfo of carrier C is configured as own, indicating self-scheduling. That is, the configuration of PCell is not changed, and whether SCell is allowed to schedule PCell depends on the configuration of SCell. Furthermore, cif-Presence is configured as true (CIF domain exists) or false (CIF domain does not exist), indicating whether there is a CIF bit domain. Furthermore, there are restrictions on the self-scheduling function of PCell. Optionally, the self-scheduled DCI sent on PCell does not have a CIF domain. When the scheduling cell information of PCell is configured as own, cif-Presence does not exist, or cif-Presence is always configured as false.

[0071] For SCell (called carrier A, whose cell index ServCellIndex>0), for example, the carrier with ServCellIndex=3 is carrier A. When RRC configures CrossCarrierSchedulingConfig, the scheduling cell information schedulingCellInfo of carrier A is configured as own, that is, self-scheduling. Further, cif-Presence is configured as true, and the CIF bit field exists. Furthermore, configure whether to schedule PCell. Method 1: First configure whether to allow scheduling of PCell. Secondly, when scheduling of PCell is not allowed, there is no need to configure the CIF value of PCell in the scheduling carrier; when scheduling of PCell is allowed, it is necessary to configure the CIF value of PCell in the scheduling carrier. Method 2: Only configure the CIF value of PCell in the scheduling carrier. For method 2, a further method for indicating whether scheduling of PCell is allowed is one of the following: method 2-1: When the CIF value of PCell in the scheduling carrier is configured, for example, an integer between 1 and 7, it indicates that scheduling of PCell is allowed; when the CIF value of PCell in the scheduling carrier is not configured, it indicates that scheduling of PCell is not allowed. Method 2-2: When the CIF value of PCell in the scheduling carrier is configured, for example, an integer between 1 and 7, it indicates that scheduling of PCell is allowed; when the CIF value is configured as 0, it indicates that scheduling of PCell is not allowed.

[0072] For example, the CrossCarrierSchedulingConfig information element is modified as follows (method 2-1): add the configuration of the CIF value of PCell in the scheduling carrier. When the CIF value of PCell in the scheduling carrier is configured, that is, cif-InSchedulingCellforPCell is configured as an integer between 1 and 7, it means that PCell scheduling is allowed; when the CIF value of PCell in the scheduling carrier is not configured, that is, cif-InSchedulingCellforPCell is not configured, it means that PCell scheduling is not allowed. Note that cif-InSchedulingCellforPCell is optional at this time.

[0073]

[0074]

[0075] For example, the CrossCarrierSchedulingConfig information element is modified as follows (method 2-2): add the CIF value of the PCell in the scheduling carrier. When the CIF value of the PCell in the scheduling carrier is configured and is an integer from 1 to 7, that is, cif-InSchedulingSCellforPCell is configured as an integer between 1-7, it means that scheduling of the PCell is allowed; when the CIF value of the PCell in the scheduling carrier is configured to be 0, that is, cif-InSchedulingSCellforPCell is configured to be 0, it means that scheduling of the PCell is not allowed. Because the CIF value of 0 is used for the self-scheduling of the SCell, that is, when there is a CIF field, CIF=0 indicates the SCell itself.

[0076]

[0077]

[0078] Further, the number of scheduled carrier indices of the primary cell is configured as a preset number, wherein the preset number may be a positive integer such as 1, 2, or 3. In this way, the number of SCells that schedule PCells is limited, and preferably, the preset number is 1, that is, only one SCell is supported to schedule PCell.

[0079] In summary, in this implementation, SCell schedules PCell, and PCell also has a self-scheduling function.

[0080] Through this implementation, when the CIF field exists in the self-scheduling own in the scheduling cell information schedulingCellInfo in the basic structure of the current CrossCarrierSchedulingConfig configuration, the configuration is added to determine whether to allow scheduling of PCell and the CIF value when scheduling PCell. And the configuration of PCell itself does not need to be modified, and it still has the self-scheduling function. At this time, when PCell is self-scheduling, there is no CIF field or there is CIF and CIF=0 to indicate scheduling of PCell; when cross-carrier scheduling by SCell is allowed, the DCI of the corresponding scheduled PCell is received according to the CIF value configured for PCell on SCell (for example, when CIF=1).

[0081] The configuration method for scheduling the main cell provided by this implementation mode further configures the main cell to be allowed to be scheduled by extending the secondary cell configuration to be self-scheduling, thereby realizing the function of the secondary cell scheduling the main cell. This can reduce the demand for the control resources of the main cell, better share the control overhead of the main cell through the dynamic load of the secondary cell, and improve the scheduling flexibility of the 5G system when reusing the 4G spectrum.

[0082] Based on the above implementation, the configuration method for scheduling the primary cell further includes:

[0083] When the primary cell supports self-scheduling and being scheduled, the downlink control information DCI format or search space type for scheduling the primary cell is determined in one of the following ways:

[0084] The primary cell is configured with only a common search space CSS and a UE-specific search space USS carrying fallback DCI, and all USSs carrying non-fallback DCI are located in the scheduling carrier that schedules the primary cell; or,

[0085] The primary cell is configured with a CSS and a USS carrying a fallback DCI and a USS carrying a non-fallback DCI, and the USS carrying the non-fallback DCI is also completely or partially located in a scheduling carrier that schedules the primary cell; or,

[0086] The CSS / USS carrying the fallback DCI is also partially or completely located in the scheduling carrier that schedules the primary cell by adding a CIF field.

[0087] In an exemplary implementation, when SCell scheduling PCell is supported, the DCI format or search space type of the scheduled PCell is determined in one of the following ways:

[0088] Mode 1: Only CSS and USSs carrying fallback DCI (DCI format 0_0 / 1_0) are configured on PCell, and all USSs carrying non-fallback DCI (DCI format 0_1 / 1_1 / 0_2 / 1_2) are located in the SCell that schedules PCell. That is, DCI format 0_0 / 1_0 without CIF field does not support scheduling at this time, so only CSS and USSs carrying fallback DCI are configured on PCell, that is, only DCI format 0_0 / 1_0 without CIF field is supported. DCI format 0_1 / 1_1 / 0_2 / 1_2 with CIF field supports scheduling. In order to share the control overhead on PCell as much as possible, all USSs carrying non-fallback DCI are located in the SCell that schedules PCell.

[0089] Method 2: CSS and USS carrying fallback DCI and USS carrying non-fallback DCI are configured on PCell, and USS carrying non-fallback DCI is also completely or partially located in the SCell that schedules PCell. That is, DCI format 0_0 / 1_0 without CIF field does not support scheduling at this time, so CSS and USS carrying fallback DCI are configured on PCell, but in order to support a certain scheduling flexibility, USS carrying non-fallback DCI can also be configured on PCell. DCI format0_1 / 1_1 / 0_2 / 1_2 with CIF field supports scheduling. In order to flexibly load share the control overhead on PCell, USS carrying non-fallback DCI can also be at least partially located in the SCell that schedules PCell.

[0090] Mode 3: The CSS / USS carrying the fallback DCI can also be partially or completely located in the SCell that schedules the PCell by adding a CIF field. In this case, a configurable CIF field is added to DCI format 0_0 / 1_0 to support the scheduling function, thereby supporting the scheduling of the PCell in the SCell.

[0091] Further, the CSS / USS is entirely or partially located in a scheduling carrier that schedules the primary cell, including:

[0092] The CSS / USS configuration adjustment factor A adjusts the number of candidate sets located in the primary cell and the scheduling carrier that schedules the primary cell.

[0093] Further, the CSS / USS configuration adjustment factor A adjusts the number of candidate sets in the primary cell and the scheduling carrier that schedules the primary cell, including:

[0094] The number of candidate sets in the primary cell remains unchanged, and the number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L); or,

[0095] The number of candidate sets in the primary cell is A*M(L), and the number of candidate sets in the scheduling carrier that schedules the primary cell is M(L)-A*M(L); or,

[0096] The number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L), and the number of candidate sets in the primary cell is M(L)-A*M(L);

[0097] Among them, M(L) is the number of candidate sets for aggregation level L. The number of candidate sets configured for a certain aggregation level L is M(L), where L=1,2,4,8,16; for example, the primary cell configuration USS#3 includes L=1 with 8 candidate sets and L=2 with 4 candidate sets. The number of candidate sets allocated to the primary cell and the scheduling carrier that schedules the primary cell is adjusted by the adjustment factor A to M(L). Method 1: The number in the primary cell remains unchanged, and the number of candidate sets in the scheduling carrier that schedules the primary cell is A*M(L), where A is a number not less than 0. For example, when A=0.5, USS#3 in the primary cell includes L=1 with 8 candidate sets and L=2 with 4 candidate sets; USS#3 in the scheduling carrier that schedules the primary cell includes L=1 with 4 candidate sets and L=2 with 2 candidate sets. Method 2: The number of candidate sets in the primary cell is A*M(L), and the number of candidate sets in the scheduling carrier that schedules the primary cell is M(L)-A*M(L); or the number of candidate sets in the scheduling carrier that schedules the primary cell is A*M(L), and the number of candidate sets in the primary cell is M(L)-A*M(L), where A is a number not less than 0; for example, when A=0.5, USS#3 in the primary cell includes L=1 with 4 candidate sets and L=2 with 2 candidate sets; USS#3 in the scheduling carrier that schedules the primary cell includes L=1 with 4 candidate sets and L=2 with 2 candidate sets.

[0098] The method for determining the DCI format or search space type when the secondary cell schedules the primary cell provided by this implementation method reduces the demand for primary cell control resources to varying degrees when the secondary cell schedules the primary cell by classifying the DCI format and the search space type. The control overhead of the primary cell is better shared through the dynamic load of the secondary cell, thereby improving the scheduling flexibility of the 5G system when reusing the 4G spectrum.

[0099] Figure 2 A schematic diagram of the structure of a device for scheduling a primary cell is shown, the device comprising:

[0100] The cross-carrier scheduling configuration module 210 is configured to configure the cross-carrier scheduling configuration information of the carrier, so that the primary cell supports self-scheduling and being scheduled.

[0101] In one implementation, the cross-carrier scheduling configuration module 210 includes a first configuration unit, which is configured to configure the scheduling cell information of the primary cell to be scheduled when the carrier is a primary cell; and configure the scheduling carrier index of the primary cell and configure the carrier indication field CIF value of the primary cell in the scheduling carrier.

[0102] In one implementation, the cross-carrier scheduling configuration module 210 includes a second configuration unit, which is configured to configure the scheduling cell information of the main cell as self-scheduling and being scheduled when the carrier is the main cell; and configure whether there is a CIF in the main cell, configure the scheduling carrier index of the main cell and configure the CIF value of the main cell in the scheduling carrier.

[0103] In one implementation, the cross-carrier scheduling configuration module 210 includes a third configuration unit, which is configured to configure the scheduling cell information of the main cell as self-scheduling when the carrier is the main cell; and configure whether the main cell is allowed to be scheduled, and when allowed to be scheduled, configure the scheduling carrier index of the main cell and configure the CIF value of the main cell in the scheduling carrier.

[0104] In one implementation, the cross-carrier scheduling configuration module 210 includes a fourth configuration unit, which is configured to configure the scheduling cell information of the secondary cell as self-scheduling when the carrier is a secondary cell; and configure whether the secondary cell is allowed to schedule the main cell, and when scheduling the main cell is allowed, configure the CIF value of the main cell in the secondary cell.

[0105] In an implementation manner, the fourth configuration unit is specifically configured to explicitly configure whether the secondary cell is allowed or not to schedule the primary cell; or to determine whether the secondary cell is allowed or not to schedule the primary cell through a preset rule.

[0106] Optionally, the preset rule includes: when the CIF value of the primary cell in the secondary cell is configured, it indicates that scheduling of the primary cell is allowed; when the CIF value of the primary cell in the secondary cell is not configured, it indicates that scheduling of the primary cell is not allowed; or

[0107] When the CIF value of the configured primary cell in the secondary cell is an element in the value set X, it means that scheduling of the primary cell is allowed; when the CIF value of the configured primary cell in the secondary cell is Y and Y is not equal to any element in the value set X, it means that scheduling of the primary cell is not allowed.

[0108] In an implementation manner, the first configuration unit is further configured to: when the scheduling cell information of the primary cell is configured to be scheduled, the primary cell also has a self-scheduling capability.

[0109] Optionally, the primary cell also has a self-scheduling capability, including:

[0110] The primary cell has a self-scheduling capability and the CIF field does not exist; or the primary cell has a self-scheduling capability and whether the CIF field exists is configured through high-layer signaling.

[0111] In one implementation, the configuration device for scheduling a primary cell further includes:

[0112] The scheduling carrier index number configuration module is configured to configure the scheduling carrier index number of the primary cell to be a preset number. Optionally, the preset number is 1.

[0113] In one implementation, the third configuration unit is specifically configured as:

[0114] By explicitly configuring the primary cell to allow or not allow scheduling; or

[0115] It is determined by a preset rule whether the primary cell is allowed to be scheduled or not.

[0116] Optionally, the preset rule includes at least one of the following:

[0117] When the CIF value of the primary cell in the scheduling carrier is configured, it indicates that the primary cell is allowed to be scheduled; when the CIF value of the primary cell in the scheduling carrier is not configured, it indicates that the primary cell is not allowed to be scheduled;

[0118] When the scheduling carrier index of the primary cell is configured, it means that the primary cell is allowed to be scheduled, and when the scheduling carrier index of the primary cell is not configured, it means that the primary cell is not allowed to be scheduled.

[0119] Optionally, the preset rule includes at least one of the following:

[0120] When the configured CIF value of the primary cell in the scheduling carrier is an element in the value set X, it indicates that the primary cell is allowed to be scheduled; when the configured CIF value of the primary cell in the scheduling carrier is Y and Y is not equal to any element in the value set X, it indicates that the primary cell is not allowed to be scheduled;

[0121] When the configured scheduling carrier index value of the primary cell is an element in the value set M, it indicates that the primary cell is allowed to be scheduled; when the configured scheduling carrier index value of the primary cell is N and N is not equal to any element in the value set M, it indicates that the primary cell is not allowed to be scheduled.

[0122] In one implementation, the configuration device for scheduling a primary cell further includes:

[0123] The DCI format / search space division module is configured to schedule the downlink control information DCI format or search space type of the primary cell to determine one of the following methods when the primary cell supports self-scheduling and being scheduled:

[0124] The primary cell is configured with only a common search space CSS and a UE-specific search space USS carrying fallback DCI, and all USSs carrying non-fallback DCI are located in the scheduling carrier that schedules the primary cell; or,

[0125] The primary cell is configured with a CSS and a USS carrying a fallback DCI and a USS carrying a non-fallback DCI, and the USS carrying the non-fallback DCI is also completely or partially located in a scheduling carrier that schedules the primary cell; or,

[0126] The CSS / USS carrying the fallback DCI is also partially or completely located in the scheduling carrier that schedules the primary cell by adding a CIF field.

[0127] Optionally, the DCI format / search space partitioning module includes:

[0128] The candidate set quantity adjustment unit is set to the CSS / USS configuration adjustment factor A to adjust the number of candidate sets located in the primary cell and the scheduling carrier that schedules the primary cell.

[0129] Optionally, the candidate set quantity adjustment unit is specifically set to:

[0130] The number of candidate sets in the primary cell remains unchanged, and the number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L); or,

[0131] The number of candidate sets in the primary cell is A*M(L), and the number of candidate sets in the scheduling carrier that schedules the primary cell is M(L)-A*M(L); or,

[0132] The number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L), and the number of candidate sets in the primary cell is M(L)-A*M(L);

[0133] Where M(L) is the number of candidate sets of aggregation level L.

[0134] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method embodiments, and will not be repeated here.

[0135] Figure 3 A schematic diagram of the structure of a device is shown, including: a processor 310 and a memory 320. The number of processors 310 in the device can be one or more. Figure 3 In the example, a processor 310 is used. The number of memories 320 in the device may be one or more. Figure 3 A memory 320 is taken as an example. The processor 310 and the memory 320 of the device can be connected via a bus or other means. Figure 3 The example of connecting through bus is taken in the following.

[0136] As a computer-readable storage medium, the memory 320 may be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the device of the embodiment of the present application (for example, a cross-carrier scheduling configuration module in a configuration device for scheduling a primary cell). The memory 320 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 320 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 320 may further include a memory remotely arranged relative to the processor 310, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0137] The device provided above can be configured to execute any one of the methods in the embodiments of the present application.

[0138] An embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.

[0139] The above description is merely an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

[0140] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0141] In general, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[0142] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0143] The block diagram of any logic flow in the accompanying drawings of the present application can represent program steps, or can represent interconnected logic circuits, modules and functions, or can represent a combination of program steps and logic circuits, modules and functions. The computer program can be stored in a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory device and system (digital versatile disc DVD or CD disc), etc. Computer-readable media may include non-transient storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FGPA) and a processor based on a multi-core processor architecture.

[0144] By way of exemplary and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, but will not depart from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

1. A method for configuring a scheduling primary cell, characterized in that: include: Configure the cross-carrier scheduling configuration information of the carrier so that the primary cell supports self-scheduling and being scheduled; When the carrier is a primary cell, configuring the scheduling cell information of the primary cell to be scheduled; and configuring the scheduling carrier index of the primary cell and configuring the carrier indication field CIF value of the primary cell in the scheduling carrier; Alternatively, when the carrier is a primary cell, the scheduling cell information of the primary cell is configured as self-scheduling and scheduled; and whether the primary cell has a CIF, the scheduling carrier index of the primary cell is configured, and the CIF value of the primary cell in the scheduling carrier is configured; Alternatively, when the carrier is a primary cell, the scheduling cell information of the primary cell is configured as self-scheduling; and whether the primary cell is allowed to be scheduled is configured, and when scheduling is allowed, the scheduling carrier index of the primary cell is configured and the CIF value of the primary cell in the scheduling carrier is configured; When the carrier is a secondary cell, the scheduling cell information of the secondary cell is configured as self-scheduling; and whether the secondary cell is allowed to schedule the primary cell is configured, and when the primary cell is allowed to schedule, the CIF value of the primary cell in the secondary cell is configured.

2. The method according to claim 1, characterized in that: The configuring whether the secondary cell is allowed to schedule the primary cell includes: By explicitly configuring the secondary cell to allow or not allow scheduling of the primary cell; or It is determined by a preset rule whether the secondary cell is allowed to schedule the primary cell.

3. The method according to claim 2, characterized in that The preset rules include: When the CIF value of the primary cell in the secondary cell is configured, it indicates that scheduling of the primary cell is allowed; and when the CIF value of the primary cell in the secondary cell is not configured, it indicates that scheduling of the primary cell is not allowed; or When the CIF value of the configured primary cell in the secondary cell is an element in the value set X, it means that scheduling of the primary cell is allowed; when the CIF value of the configured primary cell in the secondary cell is Y and Y is not equal to any element in the value set X, it means that scheduling of the primary cell is not allowed.

4. The method according to claim 1, characterized in that: When the scheduling cell information of the primary cell is configured to be scheduled, the method further includes: The primary cell also has a self-scheduling capability.

5. The method according to claim 1, characterized in that The primary cell also has a self-scheduling capability, including: The primary cell has a self-scheduling capability and the CIF field does not exist; or the primary cell has a self-scheduling capability and whether the CIF field exists is configured through high-layer signaling.

6. The method according to claim 1, characterized in that Also includes: The number of scheduled carrier indexes of the primary cell is configured to be a preset number.

7. The method according to claim 6, characterized in that The preset number is 1.

8. The method according to claim 1, characterized in that: Configuring whether the primary cell is allowed to be scheduled includes: By explicitly configuring the primary cell to allow or not allow scheduling; or It is determined by a preset rule whether the primary cell is allowed to be scheduled or not.

9. The method according to claim 8, characterized in that The preset rules include at least one of the following: When the CIF value of the primary cell in the scheduling carrier is configured, it indicates that the primary cell is allowed to be scheduled; when the CIF value of the primary cell in the scheduling carrier is not configured, it indicates that the primary cell is not allowed to be scheduled; When the scheduling carrier index of the primary cell is configured, it means that the primary cell is allowed to be scheduled, and when the scheduling carrier index of the primary cell is not configured, it means that the primary cell is not allowed to be scheduled.

10. The method according to claim 8, characterized in that The preset rules include at least one of the following: When the configured CIF value of the primary cell in the scheduling carrier is an element in the value set X, it indicates that the primary cell is allowed to be scheduled; when the configured CIF value of the primary cell in the scheduling carrier is Y and Y is not equal to any element in the value set X, it indicates that the primary cell is not allowed to be scheduled; When the configured scheduling carrier index value of the primary cell is an element in the value set M, it indicates that the primary cell is allowed to be scheduled; when the configured scheduling carrier index value of the primary cell is N and N is not equal to any element in the value set M, it indicates that the primary cell is not allowed to be scheduled.

11. The method according to any one of claims 1 to 2 and 8, characterized in that: Also includes: When the primary cell supports self-scheduling and being scheduled, the downlink control information DCI format or search space type for scheduling the primary cell is determined in one of the following ways: The primary cell is configured with only a common search space CSS and a UE-specific search space USS carrying fallback downlink control information fallback DCI, and all USSs carrying non-fallback downlink control information non-fallback DCI are located in a scheduling carrier that schedules the primary cell; or, The primary cell is configured with a CSS and a USS carrying a fallback DCI and a USS carrying a non-fallback DCI, and the USS carrying the non-fallback DCI is also completely or partially located in a scheduling carrier that schedules the primary cell; or, The CSS / USS carrying the fallback DCI is also partially or completely located in the scheduling carrier that schedules the primary cell by adding a CIF field.

12. The method according to claim 11, characterized in that The CSS / USS is entirely or partially located in a scheduling carrier that schedules the primary cell, including: The CSS / USS configuration adjustment factor A adjusts the number of candidate sets located in the primary cell and the scheduling carrier that schedules the primary cell.

13. The method according to claim 12, characterized in that The CSS / USS configuration adjustment factor A adjusts the number of candidate sets located in the primary cell and a scheduling carrier that schedules the primary cell, including: The number of candidate sets in the primary cell remains unchanged, and the number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L); or, The number of candidate sets in the primary cell is A*M(L), and the number of candidate sets in the scheduling carrier that schedules the primary cell is M(L)-A*M(L); or, The number of candidate sets in the scheduling carrier for scheduling the primary cell is A*M(L), and the number of candidate sets in the primary cell is M(L)-A*M(L); Where M(L) is the number of candidate sets of aggregation level L.

14. A configuration device for scheduling a primary cell, characterized in that: include: A cross-carrier scheduling configuration module, configured to configure the cross-carrier scheduling configuration information of the carrier, so that the primary cell supports self-scheduling and being scheduled; The cross-carrier scheduling configuration module includes a first configuration unit, which is configured to configure the scheduling cell information of the primary cell to be scheduled when the carrier is a primary cell; and configure the scheduling carrier index of the primary cell and configure the carrier indication field CIF value of the primary cell in the scheduling carrier; The cross-carrier scheduling configuration module includes a second configuration unit, which is configured to configure the scheduling cell information of the primary cell as self-scheduling and being scheduled when the carrier is a primary cell; and configure whether the primary cell has a CIF, configure the scheduling carrier index of the primary cell, and configure the CIF value of the primary cell in the scheduling carrier; The cross-carrier scheduling configuration module includes a third configuration unit, which is configured to configure the scheduling cell information of the primary cell as self-scheduling when the carrier is a primary cell; and configure whether the primary cell is allowed to be scheduled, and when it is allowed to be scheduled, configure the scheduling carrier index of the primary cell and configure the CIF value of the primary cell in the scheduling carrier; The cross-carrier scheduling configuration module includes a fourth configuration unit, which is configured to configure the scheduling cell information of the secondary cell as self-scheduling when the carrier is a secondary cell; and configure whether the secondary cell is allowed to schedule the main cell, and when the main cell is allowed to be scheduled, configure the CIF value of the main cell in the secondary cell.

15. A device, characterized in that include: memory, and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 13.

16. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 13 is implemented.

Images