WO2021160011A1 - 调度主小区的配置方法、装置、设备及储存介质 - Google Patents

调度主小区的配置方法、装置、设备及储存介质 Download PDF

Info

Publication number
WO2021160011A1
WO2021160011A1 PCT/CN2021/075190 CN2021075190W WO2021160011A1 WO 2021160011 A1 WO2021160011 A1 WO 2021160011A1 CN 2021075190 W CN2021075190 W CN 2021075190W WO 2021160011 A1 WO2021160011 A1 WO 2021160011A1
Authority
WO
WIPO (PCT)
Prior art keywords
primary cell
scheduling
carrier
scheduled
cell
Prior art date
Application number
PCT/CN2021/075190
Other languages
English (en)
French (fr)
Inventor
石靖
郝鹏
魏兴光
刘星
肖凯
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020227030840A priority Critical patent/KR20220140552A/ko
Priority to EP21753012.0A priority patent/EP4106450A4/en
Priority to US17/799,594 priority patent/US20230084554A1/en
Publication of WO2021160011A1 publication Critical patent/WO2021160011A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10—Dynamic resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • This application relates to the field of wireless communication networks, for example, to a method, device, device, and storage medium for configuring a scheduling primary cell.
  • the primary cell PCell can schedule the secondary cell SCell, but the SCell cannot schedule the PCell.
  • DSS Dynamic Power Sharing
  • the PDCCH Physical Downlink Control Channel
  • CRS Cell Reference
  • This application provides a configuration method, device, equipment, and storage medium for scheduling a primary cell, which realizes that the primary cell supports self-scheduling and being scheduled.
  • the embodiment of the present application provides a method for configuring a scheduling primary cell, including:
  • An embodiment of the present application provides a device for configuring a scheduling primary cell, including:
  • the cross-carrier scheduling configuration module is set to configure the cross-carrier scheduling configuration information of the carrier, so that the primary cell supports self-scheduling and being scheduled.
  • An embodiment of the present application provides a device including: a memory and one or more processors; the memory is used to store one or more programs; when the one or more programs are processed by the one or more The processor executes, so that the one or more processors implement any one of the scheduling primary cell configuration methods in the embodiments of the present application.
  • An embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, implements any one of the scheduling primary cell configuration methods in the embodiments of the present application.
  • the embodiment of the present application configures the cross-carrier scheduling configuration information of the carrier to enable the primary cell to support self-scheduling and scheduling, realize the function of the secondary cell for scheduling the primary cell, and reduce the demand for the control resources of the primary cell.
  • FIG. 1 is a flowchart of a method for configuring a scheduling primary cell in an embodiment of the application
  • FIG. 2 is a schematic structural diagram of a configuration device for scheduling a primary cell in an embodiment of the application
  • Figure 3 is a schematic structural diagram of a device in an embodiment of the application.
  • the fourth generation of mobile communication technology (4G, the 4th Generation mobile communication technology) Long-Term Evolution (LTE, Long-Term Evolution)/Advanced Long-Term Evolution (LTE-Advance/LTE-A, Long-Term Evolution Advance) and the fifth generation of mobile Communication technology (5G, the 5th Generation mobile communication technology) is facing more and more demands.
  • 4G and 5G systems are studying the characteristics of supporting 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.
  • Radio Resource Control configures carriers for self-scheduling or scheduling.
  • Self-scheduling that is, receiving downlink control information (DCI) on the current carrier and scheduling the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) or physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) on the current carrier .
  • Scheduled that is, receiving DCI on another carrier and scheduling PDSCH or PUSCH on this carrier.
  • 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 carrier indicator field of carrier C in the scheduling carrier. , CIF value).
  • Cross-carrier scheduling is configured by the RRC cell cross-carrier scheduling configuration information CrossCarrierSchedulingConfig, the schedulingCellId in the CrossCarrierSchedulingConfig cell configures the scheduling carrier index, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig cell configures the carrier's CIF value in the scheduling carrier.
  • RRC configures carrier C to be cross-carrier scheduled by carrier A and configures carrier C to have a CIF value of 1 in the scheduling carrier.
  • DCI formats 1_0 and 0_0 (also known as fallback downlink control information fallback DCI) cannot be configured with the CIF domain, so DCI formats 1_0 and 0_0 can only be used for self-scheduling and cannot be used for cross-carrier scheduling; 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) can be configured with CIF domains, and they can be used for cross-carrier scheduling.
  • 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
  • the CIF field indication of the DCI (DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2) on the scheduled carrier indicates when the CIF value configured for the carrier is configured in the scheduling carrier
  • one CIF value can only correspond to one carrier.
  • a carrier can only be configured to be self-scheduled or scheduled, and cannot be configured to be self-scheduled and scheduled at the same time.
  • the primary cell can only be configured for self-scheduling, which results in the limited capacity of the PDCCH in the DSS, resulting in a high load on the 5G system to transmit control signaling.
  • the PCell in the embodiment of the present application indicates that PCell of a terminal.
  • the primary and secondary cell uses the same processing manner as the PCell described in the embodiment of this application.
  • 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.
  • RRC configures a carrier (denoted as carrier B) for self-scheduling
  • CrossCarrierSchedulingConfig it configures schedulingCellInfo of carrier B's scheduling cell information as own, that is, self-scheduling.
  • it is configured as false, there is no CIF domain, and only self-scheduled is possible at this time.
  • the scheduling cell information schedulingCellInfo of carrier C is configured as other, which means it is scheduled.
  • the value of CIF in the carrier is, for example, the value of CIF cif-InSchedulingCell is a positive integer from 1 to 7.
  • RRC configures carrier C to be cross-carrier scheduled by carrier A and configures carrier C to have a CIF value of 1 in the scheduling carrier.
  • the CIF field of the DCI on carrier A indicates that the CIF index is 1, then this DCI is scheduled on carrier C PDSCH or PUSCH.
  • the scheduling cell information of the SCell carrier can be configured as other; for a non-PCell carrier, the scheduling cell information can be configured as own or other.
  • FIG. 1 shows a flowchart of a method for configuring a scheduling primary cell, and the method includes:
  • 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 based on the original support of self-scheduling; it can also be scheduled for the secondary cell.
  • the cross-carrier scheduling configuration information of the cell carrier is configured so that the secondary cell can schedule the 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 primary cell is configured in the scheduling carrier.
  • Carrier indicator field CIF value when the carrier is the 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 primary cell is configured in the scheduling carrier.
  • the scheduling cell information schedulingCellInfo of carrier C is configured as other, that is, it is scheduled.
  • the carrier index of the scheduling carrier A (called the anchor carrier) of the carrier C (called the modulated carrier) is configured.
  • the scheduling carrier A is SCell, that is, the carrier index of the scheduling carrier A is determined by configuring the ServCellIndex corresponding to the schedulingCellId.
  • the primary cell has a self-scheduling function at the same time.
  • the primary cell has a self-scheduling capability at the same time, including: the primary cell has self-scheduling capabilities and the CIF domain does not exist; or the primary cell has self-scheduling capabilities And whether the CIF domain exists is configured through high-level signaling.
  • the scheduling cell information schedulingCellInfo of carrier A is configured to own, that is, self-scheduling
  • carrier A is configured If the cif-Presence is true, there is a CIF bit field.
  • the preset number can be a positive integer such as 1, 2, 3, etc.
  • the number of SCells for scheduling the PCell is limited.
  • the preset number is 1, that is, only one SCell can be used for scheduling the PCell.
  • SCell scheduling PCell is implemented, and PCell also has a self-scheduling function.
  • the basic structure of the CrossCarrierSchedulingConfig configuration is not changed, and only the PCell can be configured to other when schedulingCellInfo is configured. And when the PCell is configured as other, the default PCell also has a self-scheduling function.
  • the configuration of CrossCarrierSchedulingConfig for SCell does not need to be modified, and schedulingCellInfo needs to be configured as self-scheduled own when scheduling PCell.
  • the configuration method for scheduling the primary cell provided by this implementation mode, by extending the primary cell configuration as the scheduled carrier and at the same time acquiescing that the primary cell has the self-scheduling function, realizes the function of the secondary cell scheduling the primary cell, which can reduce the demand for the control resources of the primary cell , To better share the control overhead of the primary cell through the dynamic load of the secondary cell, and improve the scheduling flexibility when the 5G system reuses 4G spectrum.
  • the carrier when the carrier is the primary cell, configure the scheduling cell information of the primary cell as self-scheduled and scheduled; and configure whether the primary cell has CIF, configure the scheduling carrier of the primary cell Index and configure the CIF value of the primary cell in the scheduling carrier.
  • the scheduling cell information schedulingCellInfo for carrier C is configured to own and other, that is, both self-scheduling and scheduling are supported at the same time, that is A new option is added to schedulingCellInfo, which is own and other.
  • the modulated carrier exists (cif-Presence), the scheduling carrier index (schedulingCellId), and the value of CIF (cif-InSchedulingCell).
  • the self-scheduling DCI sent on the PCell does not have the CIF field. That is, in the own and other option, there is no cif-Presence, or Presence is always configured as false.
  • the scheduling cell information schedulingCellInfo is configured for carrier A as own, that is, self-scheduling, and cif- If Presence is set to true, there is a CIF bit field.
  • the preset number can be a positive integer such as 1, 2, 3, etc.
  • the number of SCells for scheduling the PCell is limited.
  • the preset number is 1, that is, only one SCell can be used for scheduling the PCell.
  • SCell scheduling PCell is implemented, and PCell also has a self-scheduling function.
  • an option is added to schedulingCellInfo in the basic structure configured by CrossCarrierSchedulingConfig, which is self-scheduled and scheduled own and other.
  • CrossCarrierSchedulingConfig which is self-scheduled and scheduled own and other.
  • the configuration of CrossCarrierSchedulingConfig for SCell does not need to be modified, and schedulingCellInfo needs to be configured as self-scheduled own when scheduling PCell.
  • the configuration method for scheduling the primary cell provided by this implementation mode, by extending the primary cell configuration to increase the configuration of the scheduled carrier when self-scheduled, realizes the function of the secondary cell scheduling the primary cell, which can reduce the demand for the control resources of the primary cell, and more It is good to share the control overhead of the primary cell through the dynamic load of the secondary cell to improve the scheduling flexibility when the 5G system reuses the 4G spectrum.
  • the carrier when the carrier is the primary cell, configure the scheduling cell information of the primary cell as self-scheduling; and configure whether the primary cell is allowed to be scheduled, and configure the primary cell when it is allowed to be scheduled.
  • the scheduling carrier index of and configuring the CIF value of the primary cell in the scheduling carrier when the carrier is the primary cell, configure the scheduling cell information of the primary cell as self-scheduling; and configure whether the primary cell is allowed to be scheduled, and configure the primary cell when it is allowed to be scheduled.
  • the scheduling cell information schedulingCellInfo for carrier C is configured to be own, which means self-scheduling.
  • configuring whether the primary cell is allowed to be scheduled includes: configuring whether the primary cell is allowed or not allowed to be scheduled by displaying; or determining whether the primary cell is allowed or not allowed to be scheduled through 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 means 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 means 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.
  • the scheduling carrier index of the primary cell indicates that the primary cell is not allowed to be scheduled. In an exemplary implementation manner, only the SCell carrier index for scheduling the PCell and the CIF value used by the PCell are indicated when the SCell schedules the PCell.
  • How to indicate whether the PCell is allowed to be scheduled is one of the following methods: (1) When the CIF value is configured, for example, an integer between 1 and 7, indicates that the PCell is allowed to be scheduled, and when the CIF value is not configured, it indicates that it is not allowed Scheduling the PCell; (2) When the SCell index of the scheduling PCell is configured, for example, an integer between 1 and 31, indicating that the PCell is allowed to be scheduled, and when the SCell index of the scheduling PCell is not configured, it indicates that the scheduling of the PCell is not allowed.
  • the CrossCarrierSchedulingConfig information element is modified as follows: add the SCell carrier index for the scheduling PCell and the CIF value of the PCell used by the SCell when the PCell is scheduled.
  • SCell carrier index for the scheduling PCell and the CIF value of the PCell are configured
  • the schedulingSCellId is configured as an integer between 1 and 31 (that is, when the schedulingSCellId configurable value ServCellIndex is an integer between 1 and 31)
  • cif-InSchedulingSCellforPCell is an integer between 1 and 7, it means that the PCell is allowed to be scheduled ;
  • the SCell carrier index of the scheduling PCell and the CIF value of the PCell are not configured, that is, the schedulingSCellId and cif-InSchedulingSCellforPCell are not configured, which means that the PCell is not allowed to be scheduled.
  • schedulingSCellId and cif-InSchedulingSCellforPCell are optional.
  • the preset rule also includes 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 means that the primary cell is allowed to be scheduled, and when the configured primary cell is scheduling When the CIF value in the carrier is Y and Y is not equal to any element in the value set X, it means that the primary cell is not allowed to be scheduled; the configured scheduling carrier index of the primary cell is an element in the value set M When, it means that the primary cell is allowed to be scheduled. When the configured scheduling carrier index of the primary cell takes a value of N and N is not equal to any element in the value set M, it means that the primary cell is not allowed to be scheduled.
  • the element in the value set X is an integer greater than 0, such as an integer from 1 to 7, and Y is 0, for example.
  • the elements in the value set M are integers greater than 0, such as integers from 1 to 31, and N is 0, for example.
  • the method for indicating whether PCell is allowed to be scheduled is one of the following: (1) When a CIF value is configured, for example, an integer between 1 and 7, indicating that PCell is allowed to be scheduled, when When the configured CIF value is 0, it means that the PCell is not allowed to be scheduled; (2) When the SCell carrier index for scheduling the PCell is configured, for example, an integer between 1 and 31, which means that the PCell is allowed to be scheduled, and when the SCell index for scheduling the PCell is configured When it is 0, it means that PCell is not allowed to be scheduled.
  • the CrossCarrierSchedulingConfig cell is modified as follows: Add the SCell carrier index of the configured PCell and the PCell CIF value when the SCell schedules the PCell.
  • SCell carrier index of the scheduling PCell and the PCell CIF value are configured, it is configured
  • schedulingSCellId is 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 configured scheduling PCell is set to 0, and/or the CIF of the PCell is taken
  • the value is 0, that is, the schedulingSCellId is configured to be 0, and/or the cif-InSchedulingCellforPCell is 0, which means that the PCell is not allowed to be scheduled.
  • CIF with a value of 0 indicates the SCell itself; the schedulingSCellId with a value of 0 is the PCell.
  • the scheduling cell information schedulingCellInfo is configured for carrier A as own, that is, self-scheduling, and cif- If Presence is set to true, there is a CIF bit field.
  • the preset number can be a positive integer such as 1, 2, 3, etc.
  • the number of SCells for scheduling the PCell is limited.
  • the preset number is 1, that is, only one SCell can be used for scheduling the PCell.
  • SCell scheduling PCell is implemented, and PCell also has a self-scheduling function.
  • the scheduling cell information schedulingCellInfo in the basic structure configured by CrossCarrierSchedulingConfig is configured to add the SCell carrier index for configuring the PCell and the CIF value used by the PCell when the SCell schedules the PCell when the schedulingCellInfo is configured to self-schedule.
  • the configuration of CrossCarrierSchedulingConfig for SCell does not need to be modified, and schedulingCellInfo needs to be configured as self-scheduled own when scheduling PCell.
  • the configuration method for scheduling the primary cell provided by this implementation mode, by extending the primary cell configuration as the modulated carrier and the primary modulated carrier, realizes the function of the secondary cell to schedule the primary cell, which can reduce the demand for the primary cell's control resources and better pass
  • the secondary cell dynamically load shares the control overhead of the primary cell and improves the scheduling flexibility when the 5G system reuses 4G spectrum.
  • the carrier when the carrier is a secondary cell, configure the scheduling cell information of the secondary cell as self-scheduling; and configure whether the secondary cell allows the primary cell to be scheduled, and when the primary cell is allowed to be scheduled, configure the The CIF value of the primary cell in the secondary cell.
  • the configuring whether the secondary cell allows the primary cell to be scheduled includes: configuring the secondary cell to allow or not allow the primary cell to be scheduled; or determine whether the secondary cell allows or not to allow the primary cell to be scheduled through a preset rule Community.
  • 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, and when the CIF value of the primary cell in the secondary cell is not configured , 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, and when the configured primary cell is in all When the CIF value in the secondary cell is Y and Y is not equal to any element in the value set X, it means that the primary cell is not allowed to be scheduled.
  • the elements in the value set X are integers greater than 0, for example, integers from 1 to 7.
  • the schedulingCellInfo configuration of carrier C is configured to own, which means self-scheduling. That is, the configuration of the PCell is not changed, and whether the SCell is allowed to schedule the PCell depends on the configuration of the SCell. Configure cif-Presence to be true (there is a CIF field) or false (there is no CIF field), indicating whether there is a CIF bit field. There are restrictions on the PCell having the self-scheduling function. Optionally, the self-scheduling DCI sent on the PCell does not have the CIF field. When the scheduling cell information of PCell is configured as own, there is no cif-Presence, or cif-Presence is always configured as false.
  • the scheduling cell information schedulingCellInfo is configured for carrier A as own, that is, self-scheduling, and cif- If Presence is set to true, there is a CIF bit field.
  • Method 1 First configure whether to allow PCell to be scheduled. Secondly, when the PCell is not allowed to be scheduled, the CIF value of the PCell in the scheduling carrier does not need to be configured; when the PCell is allowed to be scheduled, the CIF value of the PCell in the scheduling carrier needs to be configured.
  • Method 2 Only configure the CIF value of the PCell in the scheduling carrier. For method 2, how to indicate whether the PCell is allowed to be scheduled is one of the following methods.
  • Method 2-1 When the CIF value of the PCell in the scheduling carrier is configured, for example, an integer between 1 and 7, indicating that the PCell is allowed to be scheduled , When the CIF value of the PCell in the scheduling carrier is not configured, it means that the PCell is not allowed to be scheduled.
  • the CrossCarrierSchedulingConfig cell is modified as follows (Method 2-1): Add the CIF value of the PCell in the scheduling carrier.
  • the CIF value of the PCell in the scheduling carrier is configured
  • the cif-InSchedulingCellforPCell is set to 1.
  • it is an integer between -7, it means that the PCell is allowed to be scheduled;
  • the CIF value of the PCell in the scheduling carrier is not configured, that is, cif-InSchedulingCellforPCell is not configured, which means that the PCell is not allowed to be scheduled.
  • cif-InSchedulingCellforPCell is optional.
  • the preset number can be a positive integer such as 1, 2, 3, etc.
  • the number of SCells for scheduling the PCell is limited.
  • the preset number is 1, that is, only one SCell can be used for scheduling the PCell.
  • SCell scheduling PCell is implemented, and PCell also has a self-scheduling function.
  • the configuration method for scheduling the primary cell provided by this implementation mode, by extending the secondary cell configuration to allow the scheduling of the primary cell when self-scheduled, realizes the function of the secondary cell for scheduling the primary cell, which can reduce the demand for the control resources of the primary cell, and better Through the secondary cell dynamic load sharing of the control overhead of the primary cell, the scheduling flexibility of the 5G system when the 4G spectrum is reused is improved.
  • the method for configuring the scheduling primary cell further includes:
  • the downlink control information DCI format or search space type for scheduling the primary cell is determined by one of the following methods:
  • a common search space Common Search Space, CSS
  • a UE-specific search space UE Specific Search Space, USS
  • the primary cell is configured with CSS and the USS carrying fallback DCI and the USS carrying non-fallback DCI, and the USS carrying non-fallback DCI is also fully or partially located in the scheduling carrier of the primary cell
  • the CSS/USS that bears the fallback DCI is also partly or completely located in the scheduling carrier that schedules the primary cell by adding a CIF field.
  • the DCI format or search space type of scheduling PCell is determined by one of the following methods:
  • Method 1 Only CSS and USS carrying fallback DCI (DCI format 0_0/1_0) are configured on the PCell, and the USS carrying non-fallback DCI (DCI format 0_1/1_1/0_2/1_2) is all located in the SCell where the PCell is scheduled. That is, DCI format 0_0/1_0 without CIF domain does not support cross-carrier scheduling of other carriers. Therefore, only CSS and USS carrying fallback DCI are configured on the PCell, that is, only DCI format 0_0/1_0 without CIF domain is supported. The DCI format 0_1/1_1/0_2/1_2 with the CIF domain supports scheduling. In order to share the control overhead on the PCell to the greatest possible load, the USS carrying non-fallback DCI is all located in the SCell where the PCell is scheduled.
  • Manner 2 CSS, USS carrying fallback DCI, and USS carrying non-fallback DCI are configured on the PCell.
  • the USS carrying non-fallback DCI is also all or partly located in the SCell that schedules the PCell. That is to say, DCI format without CIF domain at this time 0_0/1_0 does not support cross-carrier scheduling of other carriers, so the PCell is configured with CSS and the USS carrying fallback DCI, but in order to support certain scheduling flexibility, PCell can also be configured to carry non- fallback DCI's USS.
  • the DCI format 0_1/1_1/0_2/1_2 with the CIF domain supports scheduling.
  • the USS carrying non-fallback DCI may also be at least partially located in the SCell where the PCell is scheduled.
  • the CSS/USS carrying the fallback DCI can also be partially or completely located in the SCell scheduling the PCell by adding a CIF field.
  • a configurable CIF field is added to the DCI format 0_0/1_0 to support the scheduled function, and further support the scheduling of the PCell in the SCell.
  • the CSS/USS is all or partly located in the scheduling carrier for scheduling the primary cell, including:
  • An adjustment factor A is configured for the CSS/USS, and the number of candidate sets located in the primary cell and the scheduling carrier that schedules the primary cell is adjusted.
  • Configuring an adjustment factor A for the CSS/USS and adjusting the number of candidate sets in the primary cell and the scheduling carrier that schedules the primary cell includes:
  • 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),
  • the number of candidate sets in the scheduling carrier for scheduling 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 primary cell is The number of candidate sets in the cell is M(L)-A*M(L); where M(L) is the number of candidate sets of aggregation level L.
  • the number of candidate sets in the scheduling carrier allocated to the primary cell and the scheduling 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 for scheduling the primary cell is A*M(L), and A is a number not less than 0 at this time.
  • 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 of the scheduling primary cell is M(L)-A*M(L); or the candidate set in the scheduling carrier of the scheduling primary cell
  • the number is A*M(L)
  • the number of candidate sets in the primary cell is M(L)-A*M(L)
  • the method for determining the DCI format or search space type when the secondary cell schedules the primary cell is provided by this implementation mode.
  • the secondary cell scheduling the primary cell can reduce the control of the primary cell to varying degrees. Resource requirements can better share the control overhead of the primary cell through the dynamic load of the secondary cell, and improve the scheduling flexibility when the 5G system reuses 4G spectrum.
  • Fig. 2 shows a schematic structural diagram of a configuration device for scheduling a primary cell, and the device includes:
  • 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 is scheduled.
  • the cross-carrier scheduling configuration module 210 includes a first configuration unit configured to configure the scheduling cell information of the primary cell to be scheduled when the carrier is the primary cell; and configure the primary cell's information Scheduling carrier index and configuring the carrier indication field CIF value of the primary cell in the scheduling carrier.
  • the cross-carrier scheduling configuration module 210 includes a second configuration unit configured to configure the scheduling cell information of the primary cell as self-scheduled and scheduled when the carrier is the primary cell; and configure the Whether there is a CIF in the primary cell, 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 210 includes a third configuration unit configured to configure the scheduling cell information of the primary cell as self-scheduling when the carrier is the primary cell; and whether to configure the primary cell Scheduling is allowed, and when scheduling is allowed, the scheduling carrier index of the primary cell and the CIF value of the primary cell in the scheduling carrier are configured.
  • the cross-carrier scheduling configuration module 210 includes a fourth configuration unit configured to configure the scheduling cell information of the secondary cell as self-scheduling when the carrier is a secondary cell; and whether to configure the secondary cell
  • the primary cell is allowed to be scheduled, and when the primary cell is allowed to be scheduled, the CIF value of the primary cell in the secondary cell is configured.
  • the fourth configuration unit is configured to display and configure the secondary cell to allow or disallow scheduling of the primary cell; or determine whether the secondary cell allows or disallows scheduling of the primary cell through a preset rule.
  • 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, and when the primary cell is not configured in the secondary cell, When the CIF value is selected, it means 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 means that the primary cell is allowed to be scheduled. When the 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 means that the primary cell is not allowed to be scheduled.
  • 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 has a self-scheduling capability at the same time.
  • the primary cell has a self-scheduling capability at the same time, including:
  • the primary cell has self-scheduling capability and the CIF domain does not exist; or the primary cell has self-scheduling capability and whether the CIF domain exists is configured through high-level signaling.
  • the device for configuring the primary cell for scheduling further includes:
  • the scheduling carrier index quantity configuration module is configured to configure the scheduling carrier index quantity of the primary cell to a preset quantity.
  • the preset number is 1.
  • the third configuration unit is set as:
  • the primary cell is allowed or not allowed to be scheduled through display configuration; or, the primary cell is allowed or not allowed to be scheduled through a preset rule.
  • the preset rule includes at least one of the following:
  • the CIF value of the primary cell in the scheduling carrier when configured, it means 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 means that the primary cell is not allowed to be scheduled; when 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.
  • the preset rule includes at least one of the following:
  • the configured CIF value of the primary cell in the scheduling carrier is an element in the value set X
  • the configured CIF value of the primary cell in the scheduling carrier is Y and Y
  • it is not equal to any element in the value set X it means that the primary cell is not allowed to be scheduled
  • the configured scheduling carrier index of the primary cell is an element in the value set M
  • the configured scheduling carrier index of the primary cell takes a value of N and N is not equal to any element in the value set M, it means that the primary cell is not allowed to be scheduled.
  • the device for configuring the primary cell for scheduling further includes:
  • the DCI format/search space dividing module is configured to schedule the downlink control information DCI format or search space type of the primary cell when the primary cell supports self-scheduling and is scheduled to be determined by one of the following methods:
  • the DCI format/search space division module includes:
  • the candidate set quantity adjustment unit is configured to configure an adjustment factor A for the CSS/USS, and adjust the number of candidate sets located in the primary cell and the scheduling carrier for scheduling the primary cell.
  • the unit for adjusting the number of candidate sets is set to:
  • 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),
  • the number of candidate sets in the scheduling carrier for scheduling 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 primary cell is The number of candidate sets in the cell is M(L)-A*M(L); where M(L) is the number of candidate sets of aggregation level L.
  • FIG. 3 shows a schematic structural diagram of a device, including: a processor 310 and a memory 320.
  • the number of processors 310 in the device may be one or more.
  • One processor 310 is taken as an example in FIG. 3.
  • the number of memories 320 in the device may be one or more, and one memory 320 is taken as an example in FIG. 3.
  • the processor 310 and the memory 320 of the device may be connected by a bus or in other ways. In FIG. 3, the connection by a bus is taken as an example.
  • the memory 320 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the device in the embodiment of the present application (for example, the cross-connect in the configuration device of the scheduling primary cell). Carrier scheduling configuration module).
  • the memory 320 may include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 320 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 320 may include a memory remotely provided with respect to the processor 310, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the device provided above can be configured to execute any method in the embodiments of the present application.
  • the embodiment of the present application provides a storage medium that 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.
  • the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicular mobile stations.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of 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 (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FPGA Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

提供了一种调度主小区的配置方法、装置、设备及储存介质。调度主小区的配置包括：配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度（S110）。

Description

调度主小区的配置方法、装置、设备及储存介质
本申请要求在2020年02月12日提交中国专利局、申请号为202010089243.2的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信网络领域，例如涉及一种调度主小区的配置方法、装置、设备及存储介质。
背景技术
在5G通信系统中，主小区PCell可以调度辅小区SCell，SCell不可以调度PCell。在考虑5G系统与4G系统进行动态频谱共享(Dynamic Power Sharing，DSS)时，受限于4G系统带宽较小和避免4G系统的PDCCH(Physical Downlink Control Channel，物理下行控制信道)和CRS(Cell Reference Signal，小区参考信号)干扰等因素，5G系统使用DSS的PCell上的PDCCH资源受限。
发明内容
本申请提供一种调度主小区的配置方法、装置、设备及存储介质，实现了主小区支持自调度和被调度。
本申请实施例提供一种调度主小区的配置方法，包括：
配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度。
本申请实施例提供一种调度主小区的配置装置，包括：
跨载波调度配置模块，设置为配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度。
本申请实施例提供一种设备，包括：存储器，以及一个或多个处理器；所述存储器，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现本申请实施例中的任意一种调度主小区的配置方法。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中的任意一种调度主小区的配置方法。
本申请实施例通过配置载波的跨载波调度配置信息，使得主小区支持自调 度和被调度，实现辅小区调度主小区的功能，能够降低对主小区控制资源的需求。
附图说明
图1为本申请实施例中一种调度主小区的配置方法的流程图；
图2为本申请实施例中一种调度主小区的配置装置的结构示意图；
图3为本申请实施例中一种设备的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。
第四代移动通信技术(4G，the 4th Generation mobile communication technology)长期演进(LTE，Long-Term Evolution)/高级长期演进(LTE-Advance/LTE-A，Long-Term Evolution Advance)和第五代移动通信技术(5G，the 5th Generation mobile communication technology)所面临的需求越来越多。从发展趋势来看，4G和5G系统都在研究支持增强移动宽带、超高可靠性、超低时延传输、海量连接的特征。并且5G系统也允许通过DSS重用4G频谱。
在5G系统及标准中，无线资源控制(Radio Resource Control，RRC)配置载波进行自调度或被调度。自调度，即在当前载波上接收下行控制信息(Downlink Control Information，DCI)并调度当前载波上的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)或物理上行共享信道(Physical Uplink Shared Channel，PUSCH)。被调度，即在另外一个载波上接收DCI而调度该载波上的PDSCH或PUSCH。当RRC配置一个载波(记为载波C)为被调度时，RRC需要配置载波C的调度载波索引(即由哪个载波调度载波C)并且配置载波C在调度载波中的载波指示域(Carrier Indicator Field，CIF取值)。主调载波上的DCI中的CIF域指示载波C在调度载波中的CIF取值时，则该DCI在载波C上调度PDSCH或PUSCH。跨载波调度由RRC信元跨载波调度配置信息CrossCarrierSchedulingConfig配置，CrossCarrierSchedulingConfig信元中schedulingCellId配置调度载波索引，CrossCarrierSchedulingConfig信元中的cif-InSchedulingCell配置载波在调度载波中的CIF取值。假设RRC配置载波C由载波A跨载波调度并且配置载波C在调度载波中的CIF取值为1，当载波A上的DCI的CIF域指示的CIF取值为1时，则此DCI在载波C上调度PDSCH或PUSCH。DCI格式1_0和0_0(也称为回退下行控制信息fallback DCI)中不能配置CIF域，所以DCI格式1_0和0_0只能用于自调度而不能用于跨载波调度；DCI格式0_1、DCI格式0_2、DCI格式1_1和DCI格式1_2(也称为非回 退下行控制信息non-fallback DCI)中可以配置CIF域，它们可以用于跨载波调度。
当RRC配置载波为自调度时，DCI格式1_0只能用于调度本载波上的PDSCH，DCI格式0_0只能用于调度本载波上的PUSCH，DCI格式1_1且CIF＝0时和DCI格式1_2且CIF＝0时用于调度本载波上的PDSCH，DCI格式0_1且CIF＝0时和DCI格式0_2且CIF＝0时用于调度本载波上的PUSCH。当RRC配置载波为被调度时，调度载波上的DCI(DCI格式0_1、DCI格式0_2、DCI格式1_1和DCI格式1_2)的CIF域指示为该载波配置的在调度载波中的CIF取值时表示跨载波调度该载波，一个CIF取值只能对应一个载波。一个载波只能配置为自调度或被调度，不能同时被配置为自调度和被调度。主小区只能配置为自调度，因此导致在DSS时PDCCH容量受限，导致5G系统传输控制信令的负载较高。
由于不同用户设备(User Equipment，UE)看到的主小区(Primary Cell，PCell)可以是不同的，并且不同UE的各个载波都是独立配置的，因此本申请实施例中的所述PCell表示针对一个终端的PCell。
本申请实施例中针对PCell描述，当配置了辅小区组(Secondary Cell group，SCG)时，主辅小区(Primary Secondary Cell，PSCell)与本申请实施例所述PCell使用相同的处理方式。本申请实施例中所述主小区的跨载波调度配置信息配置方式针对PCell或PSCell都是适用的。
当RRC配置一个载波(记为载波B)为自调度时，RRC配置CrossCarrierSchedulingConfig时会将载波B的调度小区信息schedulingCellInfo配置为own，即自调度。对non-fallback DCI中是否有CIF域通过cif-Presence配置，当配置为true时，则有CIF比特域，且CIF＝0表示自调度，即调度载波B，其他CIF取值时表示调度其他载波；当配置为false时，无CIF域，此时仅可以自调度。
当RRC配置一个载波(记为载波C)为被调度时，RRC配置CrossCarrierSchedulingConfig时会将载波C的调度小区信息schedulingCellInfo配置为other，即被调度。配置调度载波C的载波A的载波索引，即载波A的调度载波索引通过配置schedulingCellId对应的ServCellIndex确定，其中PCell的ServCellIndex＝0，其他Cell的载波索引也是高层信令配置的；配置载波C在调度载波中的CIF取值，示例地CIF取值cif-InSchedulingCell为1至7的正整数。假设RRC配置载波C由载波A跨载波调度并且配置载波C在调度载波中的CIF取值为1，当载波A上的DCI的CIF域指示CIF索引为1时，则此DCI在载波C上调度PDSCH或PUSCH。
相关技术中，仅可以对SCell的载波的调度小区信息配置为other；对于一个非PCell的载波，调度小区信息能配置为own或other。
本申请实施例中，图1示出一种调度主小区的配置方法的流程图，该方法包括：
S110、配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度。
相关技术中主小区的调度小区信息仅能配置为own，也就是自调度。那么，想要实现主小区支持自调度和被调度，可以对主小区载波的跨载波调度配置信息进行配置，使得主小区在原本支持自调度的基础上，可以配置为被调度；也可以对辅小区载波的跨载波调度配置信息进行配置，使得辅小区可以调度主小区。
在一种实现方式中，当所述载波为主小区时，配置所述主小区的调度小区信息为被调度；且配置所述主小区的调度载波索引和配置所述主小区在调度载波中的载波指示域CIF取值。
在载波聚合(Carrier aggregation，CA)场景时，针对PCell(记为载波C，其载波索引ServCellIndex＝0)进行RRC配置CrossCarrierSchedulingConfig时，对载波C的调度小区信息schedulingCellInfo配置为other，即被调度。此时配置载波C(称为被调载波)的调度载波A(称为主调载波)的载波索引，此时调度载波A为SCell，即调度载波A的载波索引通过配置schedulingCellId对应的ServCellIndex确定，且调度载波A的ServCellIndex>0，可选为1至31之间的整数，例如ServCellIndex＝3；配置载波C在调度载波A中的CIF取值，可选CIF取值cif-InSchedulingCell为1至7的正整数，例如CIF＝1。
此时，主小区同时具有自调度功能，可选的，所述主小区同时具有自调度能力，包括：所述主小区具有自调度能力且CIF域不存在；或所述主小区具有自调度能力且CIF域是否存在通过高层信令配置。
针对SCell(称为载波A，其小区索引ServCellIndex>0)，例如ServCellIndex＝3的载波为载波A，RRC配置CrossCarrierSchedulingConfig时，对载波A配置调度小区信息schedulingCellInfo配置为own，即自调度，配置载波A的cif-Presence为true，存在CIF比特域。
配置所述主小区的调度载波索引数量为预设数量。其中，预设数量可以为1、2、3等正整数。如此对调度PCell的SCell数量进行限制，例如，预设数量为1，即仅支持1个SCell可以调度PCell。
综上，在该实现方式中，实现SCell调度PCell，同时PCell也具备自调度功能。
通过该实现方式，不改变CrossCarrierSchedulingConfig配置的基本结构，仅对PCell配置schedulingCellInfo时可以配置为other的情况。并且在PCell被配置为other的情况下，默认PCell同时具有自调度功能。此时当PCell自调度时，无CIF域或有CIF且CIF＝0表示调度PCell；当被SCell跨载波调度时，按照配置的CIF值(例如CIF＝1时)接收对应PCell的DCI。此时针对SCell的CrossCarrierSchedulingConfig配置不用修改，当调度PCell时需要对schedulingCellInfo配置为自调度own。
通过该实现方式提供的调度主小区的配置方法，通过扩展主小区配置为被调度载波且同时默认主小区具有自调度功能，实现辅小区调度主小区的功能，能够降低对主小区控制资源的需求，更好的通过辅小区动态负载分担主小区的控制开销，提升5G系统重用4G频谱时的调度灵活性。
在一种实现方式中，当所述载波为主小区时，配置所述主小区的调度小区信息为自调度和被调度；且配置所述主小区是否存在CIF，配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
在CA场景时，针对PCell(称为载波C，其小区索引ServCellIndex＝0)进行RRC配置CrossCarrierSchedulingConfig时，对载波C配置调度小区信息schedulingCellInfo为own and other，即自调度和被调度同时支持，也就是对schedulingCellInfo增加新的选项，为own and other。此时配置载波C(称为被调载波)的CIF域是否存在(cif-Presence)、调度载波索引(schedulingCellId)和CIF取值(cif-InSchedulingCell)。其中CIF取值为主调载波SCell(称为调度载波A)在调度载波C时，指示载波C使用的CIF取值。例如：cif-Presence配置为false，此时载波C不支持CIF域，即载波C不支持跨载波调度其他载波；配置调度载波A(称为主调载波)的载波索引，此时调度载波A为SCell，即调度载波A的载波索引通过配置schedulingCellId对应的ServCellIndex确定，且调度载波A的ServCellIndex>0，可选为1至31之间的整数，例如ServCellIndex＝2；配置载波C在调度载波A中的CIF取值，可选CIF取值(cif-InSchedulingCell)配置为1至7之间的整数，例如CIF＝3。
例如，对CrossCarrierSchedulingConfig信元修改如下所示：
CrossCarrierSchedulingConfig information element
Figure PCTCN2021075190-appb-000001
Figure PCTCN2021075190-appb-000002
对PCell具有自调度功能存在限制，可选的，PCell上发送自调度的DCI不具有CIF域。即own and other选项中，不存在cif-Presence，或者Presence总是配置为false。
在schedulingCellInfo中新增加的own and other选项，仅限制可以对PCell配置，即对调度载波索引ServCellIndex为0的载波可以配置，对于ServCellIndex>0的不可以配置该新增选项。或者仅限制可以对PCell或PSCell 配置该新增选项，其中ServCellIndex＝0为PCell，PSCell的ServCellIndex为可配置的取值，可选为1至31之间的整数。
针对SCell(称为载波A，其小区索引ServCellIndex>0)，例如ServCellIndex＝3的载波为载波A，RRC配置CrossCarrierSchedulingConfig时，对载波A配置调度小区信息schedulingCellInfo配置为own，即自调度，配置cif-Presence配为true，存在CIF比特域。
配置所述主小区的调度载波索引数量为预设数量。其中，预设数量可以为1、2、3等正整数。如此对调度PCell的SCell数量进行限制，例如，预设数量为1，即仅支持1个SCell可以调度PCell。
综上，在该实现方式中，实现SCell调度PCell，同时PCell也具备自调度功能。
通过本实施例，对CrossCarrierSchedulingConfig配置的基本结构中调度小区信息schedulingCellInfo增加一种选项，自调度和被调度own and other。此时当自调度时，无CIF域或有CIF且CIF＝0表示调度PCell；当被SCell跨载波调度时，按照配置的在调度载波中的CIF值(例如CIF＝1时)接收对应SCell的DCI。此时针对SCell的CrossCarrierSchedulingConfig配置不用修改，当调度PCell时需要对schedulingCellInfo配置为自调度own。
通过该实现方式提供的调度主小区的配置方法，通过扩展主小区配置为自调度时增加作为被调度载波的配置，实现辅小区调度主小区的功能，能够降低对主小区控制资源的需求，更好的通过辅小区动态负载分担主小区的控制开销，提升5G系统重用4G频谱时的调度灵活性。
在一种实现方式中，当所述载波为主小区时，配置所述主小区的调度小区信息为自调度；且配置所述主小区是否允许被调度，当允许被调度时配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
在CA场景时，针对PCell(称为载波C，其小区索引ServCellIndex＝0)进行RRC配置CrossCarrierSchedulingConfig时，对载波C配置调度小区信息schedulingCellInfo为own，表示自调度。配置是否允许SCell调度PCell，当允许时配置该SCell的载波索引以及SCell调度PCell时指示PCell使用的CIF取值，例如配置SCell的ServCellIndex＝3以及SCell调度PCell时指示PCell使用的CIF＝1。
可选的，配置所述主小区是否允许被调度，包括：通过显示配置所述主小区允许或不允许被调度；或通过预设规则确定所述主小区允许或不允许被调度。
对于通过显示配置所述主小区允许或不允许被调度，在一种示例性的实现 方式中，首先配置是否允许SCell调度PCell。其次，当不允许SCell调度PCell时，无需配置该SCell的载波索引以及SCell调度PCell时指示PCell使用的CIF取值；当允许调度PCell时，需要配置该SCell的载波索引以及SCell调度PCell时指示PCell使用的CIF取值。
对于通过预设规则确定所述主小区允许或不允许被调度，预设规则包括以下至少之一：当配置了所述主小区在调度载波中的CIF取值时，表示主小区允许被调度，当不配置所述主小区在调度载波中的CIF取值时，表示主小区不允许被调度；当配置了所述主小区的调度载波索引时，表示主小区允许被调度，当不配置所述主小区的调度载波索引时，表示主小区不允许被调度。在一种示例性的实现方式中，仅配置调度PCell的SCell载波索引以及SCell调度PCell时指示PCell使用的CIF取值。如何表示是否允许调度PCell的方法为以下之一，(1)当配置了CIF取值时，例如1至7之间的一个整数，表示允许调度PCell，当不配置CIF取值时，表示不允许调度PCell；(2)当配置了调度PCell的SCell索引时，例如1至31之间的一个整数，表示允许调度PCell，当不配置调度PCell的SCell索引时，表示不允许调度PCell。
例如，对CrossCarrierSchedulingConfig信元修改如下所示：增加配置调度PCell的SCell载波索引和该SCell调度PCell时指示PCell使用的PCell的CIF取值，当配置了调度PCell的SCell载波索引和PCell的CIF取值时，即配置schedulingSCellId为1-31之间的整数时(即此时schedulingSCellId可配置值ServCellIndex为1-31之间的整数)，cif-InSchedulingSCellforPCell为1-7之间的整数时，表示允许调度PCell；当没有配置调度PCell的SCell载波索引和PCell的CIF取值时，即不配置schedulingSCellId和cif-InSchedulingSCellforPCell，表示不允许调度PCell。此时schedulingSCellId和cif-InSchedulingSCellforPCell是可选的。
CrossCarrierSchedulingConfig information element
Figure PCTCN2021075190-appb-000003
Figure PCTCN2021075190-appb-000004
预设规则还包括以下至少之一：配置的所述主小区在调度载波中的CIF取值为取值集合X中的元素时，表示主小区允许被调度，当配置的所述主小区在调度载波中的CIF取值为Y且Y不等于取值集合X中任何一个元素时，表示主小区不允许被调度；配置的所述主小区的调度载波索引取值为取值集合M中的元素时，表示主小区允许被调度，当配置的所述主小区的调度载波索引取值为N且N不等于取值集合M中任何一个元素时，表示主小区不允许被调度。其中，取值集合X中的元素为大于0的整数，例如为1至7的整数，Y例如为0。取值集合M中的元素为大于0的整数，例如为1至31的整数，N例如为0。在一种示例性的实现方式中，如何表示是否允许调度PCell的方法为以下之一，(1)当配置了CIF取值时，例如1至7之间的一个整数，表示允许调度PCell，当配置CIF取值为0时，表示不允许调度PCell；(2)当配置了调度PCell的SCell载波索引时，例如1至31之间的一个整数，表示允许调度PCell，当配置调度PCell的SCell索引为0时，表示不允许调度PCell。
例如，对CrossCarrierSchedulingConfig信元修改如下所示：增加配置PCell的SCell载波索引和该SCell调度PCell时的PCell的CIF取值，当配置了调度PCell的SCell载波索引和PCell的CIF取值时，即配置schedulingSCellId为1-31之间的整数时，cif-InSchedulingSCellforPCell为1-7之间的整数时，表示允许调度PCell；当配置调度PCell的SCell索引schedulingSCellId取值为0时，和/或PCell的CIF取值为0时，即配置schedulingSCellId为0，和/或cif-InSchedulingCellforPCell为0，表示不允许调度PCell。因为取值为0的CIF用于该SCell自调度，即存在CIF域时CIF＝0是指示该SCell自己的；取值为0的schedulingSCellId为PCell。
CrossCarrierSchedulingConfig information element
Figure PCTCN2021075190-appb-000005
Figure PCTCN2021075190-appb-000006
配置cif-Presence为true(存在CIF域)或false(不存在CIF域)，表示是否存在CIF比特域。对PCell具有自调度功能存在限制，可选的，PCell上发送自调度的DCI不具有CIF域。配置为own时，不存在cif-Presence，或者Presence总是配置为false。
针对SCell(称为载波A，其小区索引ServCellIndex>0)，例如ServCellIndex＝3的载波为载波A，RRC配置CrossCarrierSchedulingConfig时，对载波A配置调度小区信息schedulingCellInfo配置为own，即自调度，配置cif-Presence配为true，存在CIF比特域。
配置所述主小区的调度载波索引数量为预设数量。其中，预设数量可以为1、2、3等正整数。如此对调度PCell的SCell数量进行限制，例如，预设数量为1，即仅支持1个SCell可以调度PCell。
综上，在该实现方式中，实现SCell调度PCell，同时PCell也具备自调度功能。
通过该实现方式，对CrossCarrierSchedulingConfig配置的基本结构中调度小区信息schedulingCellInfo配置为自调度own时增加配置PCell的SCell载波索引和SCell调度PCell时指示PCell使用的CIF取值。此时当PCell自调度时，无CIF域或有CIF且CIF＝0表示调度PCell；当被SCell跨载波调度时，按照配置的CIF值(例如CIF＝1时)接收对应SCell的DCI。此时针对SCell的CrossCarrierSchedulingConfig配置不用修改，当调度PCell时需要对schedulingCellInfo配置为自调度own。
通过该实现方式提供的调度主小区的配置方法，通过扩展主小区配置为被调载波和主调载波，实现辅小区调度主小区的功能，能够降低对主小区控制资源的需求，更好的通过辅小区动态负载分担主小区的控制开销，提升5G系统重用4G频谱时的调度灵活性。
在一种实现方式中，当所述载波为辅小区时，配置所述辅小区的调度小区信息为自调度；且配置所述辅小区是否允许调度主小区，当允许调度主小区时配置所述主小区在所述辅小区中的CIF取值。
可选的，所述配置所述辅小区是否允许调度主小区，包括：通过显示配置 所述辅小区允许或不允许调度主小区；或通过预设规则确定所述辅小区允许或不允许调度主小区。
所述预设规则包括：当配置了所述主小区在所述辅小区中的CIF取值时，表示允许调度主小区，当不配置所述主小区在所述辅小区中的CIF取值时，表示不允许调度主小区；或配置的所述主小区在所述辅小区中的CIF取值为取值集合X中的元素时，表示允许调度主小区，当配置的所述主小区在所述辅小区中的CIF取值为Y且Y不等于取值集合X中任何一个元素时，表示不允许调度主小区。取值集合X中的元素为大于0的整数，例如为1至7的整数。
在CA场景时，针对PCell(称为载波C，其小区索引ServCellIndex＝0)进行RRC配置CrossCarrierSchedulingConfig时，对载波C配置调度小区信息schedulingCellInfo配置为own，表示自调度。即对PCell的配置不改动，是否允许SCell调度PCell取决于SCell的配置。配置cif-Presence配为true(存在CIF域)或false(不存在CIF域)，表示是否存在CIF比特域。对PCell具有自调度功能存在限制，可选的，PCell上发送自调度的DCI不具有CIF域。PCell的调度小区信息配置为own时，不存在cif-Presence，或者cif-Presence总是配置为false。
针对SCell(称为载波A，其小区索引ServCellIndex>0)，例如ServCellIndex＝3的载波为载波A，RRC配置CrossCarrierSchedulingConfig时，对载波A配置调度小区信息schedulingCellInfo配置为own，即自调度，配置cif-Presence配为true，存在CIF比特域。配置是否调度PCell。方法1：首先配置是否允许调度PCell。其次，当不允许调度PCell时，无需配置PCell在调度载波中的CIF取值；当允许调度PCell时，需要配置PCell在调度载波中的CIF取值。方法2：仅配置PCell在调度载波中的CIF取值。对于方法2，如何表示是否允许调度PCell的方法为以下之一，方法2-1：当配置了PCell在调度载波中的CIF取值时，例如1至7之间的一个整数，表示允许调度PCell，当不配置PCell在调度载波中的CIF取值时，表示不允许调度PCell。方法2-2：当配置了PCell在调度载波中的CIF取值时，例如1至7之间的一个整数，表示允许调度PCell，当配置CIF＝0取值时，表示不允许调度PCell。
例如，对CrossCarrierSchedulingConfig信元修改如下所示(方法2-1)：增加配置PCell在调度载波中的CIF取值，当配置了PCell在调度载波中的CIF取值时，即配置cif-InSchedulingCellforPCell为1-7之间的整数时，表示允许调度PCell；当没有配置PCell在调度载波中的CIF取值时，即不配置cif-InSchedulingCellforPCell，表示不允许调度PCell。此时cif-InSchedulingCellforPCell是可选的。
CrossCarrierSchedulingConfig information element
Figure PCTCN2021075190-appb-000007
例如，对CrossCarrierSchedulingConfig信元修改如下所示(方法2-2)：增加配置PCell在调度载波中的CIF取值，当配置了PCell在调度载波中的CIF取值且为1至7的整数时，即配置cif-InSchedulingSCellforPCell为1-7之间的整数时，表示允许调度PCell；当配置PCell在调度载波中的CIF取值为0时，即配置cif-InSchedulingSCellforPCell为0，表示不允许调度PCell。因为取值为0的 CIF用于该SCell自调度，即存在CIF域时CIF＝0是指示该SCell自己的。
CrossCarrierSchedulingConfig information element
Figure PCTCN2021075190-appb-000008
配置所述主小区的调度载波索引数量为预设数量。其中，预设数量可以为1、2、3等正整数。如此对调度PCell的SCell数量进行限制，例如，预设数量为1，即仅支持1个SCell可以调度PCell。
综上，在该实现方式中，实现SCell调度PCell，同时PCell也具备自调度功能。
通过该实现方式，对CrossCarrierSchedulingConfig配置的基本结构中调度小区信息schedulingCellInfo中的自调度own中当CIF域存在的情况下，增加配置是否允许调度PCell和SCell调度PCell时指示PCell使用的CIF取值。并且PCell自身的配置不用修改，仍然具有自调度功能。此时当PCell自调度时，无CIF域或有CIF且CIF＝0表示调度PCell；当允许被SCell跨载波调度时，按照SCell上为PCell配置的CIF值(例如CIF＝1时)接收对应调度PCell的DCI。
通过该实现方式提供的调度主小区的配置方法，通过扩展辅小区配置为自调度时配置允许调度主小区，实现辅小区调度主小区的功能，能够降低对主小区控制资源的需求，更好的通过辅小区动态负载分担主小区的控制开销，提升5G系统重用4G频谱时的调度灵活性。
基于上述实现方式，调度主小区的配置方法，还包括：
当所述主小区支持自调度和被调度时，调度所述主小区的下行控制信息DCI格式或搜索空间类型通过如下方式之一确定：
所述主小区上仅配置公共搜索空间(Common Search Space，CSS)和承载fallback DCI的UE特定的搜索空间(UE Specific Search Space，USS)，承载non-fallback DCI的USS全都位于调度所述主小区的调度载波中；或者，所述主小区上配置CSS和承载fallback DCI的USS和承载non-fallback DCI的USS，承载non-fallback DCI的USS也全部或部分位于调度所述主小区的调度载波中；或者，承载fallback DCI的CSS/USS通过增加CIF域，也部分或全部位于调度所述主小区的调度载波中。
在一种示例性的实现方式中，当支持SCell调度PCell时，调度PCell的DCI格式或搜索空间类型通过如下方式之一确定：
方式1：PCell上仅配置CSS和承载fallback DCI(DCI format 0_0/1_0)的USS，承载non-fallback DCI(DCI format 0_1/1_1/0_2/1_2)的USS全部位于调度PCell的SCell中。即此时不具有CIF域的DCI format 0_0/1_0不支持跨载波调度其他载波，因此PCell上仅配置CSS和承载fallback DCI的USS，即仅支持不具有CIF域的DCI format 0_0/1_0。具有CIF域的DCI format 0_1/1_1/0_2/1_2等支持被调度，为了最大可能的负载分担PCell上的控制开销，承载non-fallback DCI的USS全部位于调度PCell的SCell中。
方式2：PCell上配置CSS、承载fallback DCI的USS和承载non-fallback DCI的USS，承载non-fallback DCI的USS也全部或部分位于调度PCell的SCell中。即此时不具有CIF域的DCI format 0_0/1_0不支持跨载波调度其他载波，因此PCell上配置CSS和承载fallback DCI的USS，但是为了支持一定的调度灵活性， PCell上也可以配置承载non-fallback DCI的USS。具有CIF域的DCI format 0_1/1_1/0_2/1_2等支持被调度，为了灵活的负载分担PCell上的控制开销，承载non-fallback DCI的USS也可以至少部分位于调度PCell的SCell中。
方式3：承载fallback DCI的CSS/USS通过增加CIF域，也可以部分或全部位于调度PCell的SCell中。此时为DCI format 0_0/1_0增加可配置的CIF域，支持被调度功能，进而支持在SCell调度PCell。
所述CSS/USS全部或部分位于调度所述主小区的调度载波中，包括：
为所述CSS/USS配置调节因子A，调节位于所述主小区和调度所述主小区的调度载波中的候选集数量。
为所述CSS/USS配置调节因子A，调节位于所述主小区和调度所述主小区的调度载波中的候选集数量，包括：
所述主小区中的候选集数量不变，调度所述主小区的调度载波中候选集数量为A*M(L)；或者，所述主小区中候选集数量为A*M(L)，调度所述主小区的调度载波中候选集数量为M(L)-A*M(L)；或者，调度所述主小区的调度载波中候选集数量为A*M(L)，所述主小区中候选集数量为M(L)-A*M(L)；其中，M(L)为聚合等级L的候选集数量。配置一聚合等级L的候选集数量为M(L)，其中L＝1,2,4,8,16；例如主小区配置USS#3包含L＝1有8个候选集，L＝2有4个候选集。通过调节因子A对M(L)调节分配到主小区和调度主小区的调度载波中的候选集数量。方法1：主小区中的数量不变，调度主小区的调度载波中候选集数量为A*M(L)，此时A为不小于0的数。例如当A＝0.5时，主小区中USS#3包含L＝1有8个候选集，L＝2有4个候选集；调度主小区的调度载波中的USS#3包含L＝1有4个候选集，L＝2有2个候选集。方法2：主小区中候选集数量为A*M(L)，调度主小区的调度载波中候选集数量为M(L)-A*M(L)；或者调度主小区的调度载波中候选集数量为A*M(L)，主小区中候选集数量为M(L)-A*M(L)，此时A为不小于0的数；例如当A＝0.5时，主小区中USS#3包含L＝1有4个候选集，L＝2有2个候选集；调度主小区的调度载波中的USS#3包含L＝1有4个候选集，L＝2有2个候选集。
通过该实现方式提供的辅小区调度主小区时DCI格式或搜索空间类型确定方法，通过分类DCI格式以及所处的搜索空间类型，实现辅小区调度主小区的功能时不同程度的降低对主小区控制资源的需求，更好的通过辅小区动态负载分担主小区的控制开销，提升5G系统重用4G频谱时的调度灵活性。
图2示出一种调度主小区的配置装置的结构示意图，该装置包括：
跨载波调度配置模块210，设置为配置载波的跨载波调度配置信息，使得主 小区支持自调度和被调度。
在一种实现方式中，跨载波调度配置模块210包括第一配置单元，设置为当所述载波为主小区时，配置所述主小区的调度小区信息为被调度；且配置所述主小区的调度载波索引和配置所述主小区在调度载波中的载波指示域CIF取值。
在一种实现方式中，跨载波调度配置模块210包括第二配置单元，设置为当所述载波为主小区时，配置所述主小区的调度小区信息为自调度和被调度；且配置所述主小区是否存在CIF，配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
在一种实现方式中，跨载波调度配置模块210包括第三配置单元，设置为当所述载波为主小区时，配置所述主小区的调度小区信息为自调度；且配置所述主小区是否允许被调度，当允许被调度时配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
在一种实现方式中，跨载波调度配置模块210包括第四配置单元，设置为当所述载波为辅小区时，配置所述辅小区的调度小区信息为自调度；且配置所述辅小区是否允许调度主小区，当允许调度主小区时配置所述主小区在所述辅小区中的CIF取值。
在一种实现方式中，第四配置单元设置为通过显示配置所述辅小区允许或不允许调度主小区；或通过预设规则确定所述辅小区允许或不允许调度主小区。
可选的，所述预设规则包括：当配置了所述主小区在所述辅小区中的CIF取值时，表示允许调度主小区，当不配置所述主小区在所述辅小区中的CIF取值时，表示不允许调度主小区；或配置的所述主小区在所述辅小区中的CIF取值为取值集合X中的元素时，表示允许调度主小区，当配置的所述主小区在所述辅小区中的CIF取值为Y且Y不等于取值集合X中任何一个元素时，表示不允许调度主小区。
在一种实现方式中，第一配置单元还设置为：当配置所述主小区的调度小区信息为被调度时，所述主小区同时具有自调度能力。
可选的，所述主小区同时具有自调度能力，包括：
所述主小区具有自调度能力且CIF域不存在；或所述主小区具有自调度能力且CIF域是否存在通过高层信令配置。
在一种实现方式中，调度主小区的配置装置，还包括：
调度载波索引数量配置模块，设置为配置所述主小区的调度载波索引数量 为预设数量。可选的，所述预设数量为1。
在一种实现方式中，第三配置单元设置为：
通过显示配置所述主小区允许或不允许被调度；或，通过预设规则确定所述主小区允许或不允许被调度。
可选的，所述预设规则包括以下至少之一：
当配置了所述主小区在调度载波中的CIF取值时，表示主小区允许被调度，当不配置所述主小区在调度载波中的CIF取值时，表示主小区不允许被调度；当配置了所述主小区的调度载波索引时，表示主小区允许被调度，当不配置所述主小区的调度载波索引时，表示主小区不允许被调度。
可选的，所述预设规则包括以下至少之一：
配置的所述主小区在调度载波中的CIF取值为取值集合X中的元素时，表示主小区允许被调度，当配置的所述主小区在调度载波中的CIF取值为Y且Y不等于取值集合X中任何一个元素时，表示主小区不允许被调度；配置的所述主小区的调度载波索引取值为取值集合M中的元素时，表示主小区允许被调度，当配置的所述主小区的调度载波索引取值为N且N不等于取值集合M中任何一个元素时，表示主小区不允许被调度。
在一种实现方式中，调度主小区的配置装置，还包括：
DCI格式/搜索空间划分模块，设置为当所述主小区支持自调度和被调度时，调度所述主小区的下行控制信息DCI格式或搜索空间类型通过如下方式之一确定：
所述主小区上仅配置公共搜索空间CSS和承载fallback DCI的UE特定的搜索空间USS，承载non-fallback DCI的USS全都位于调度所述主小区的调度载波中；或者，所述主小区上配置CSS和承载fallback DCI的USS和承载non-fallback DCI的USS，承载non-fallback DCI的USS也全部或部分位于调度所述主小区的调度载波中；或者，承载fallback DCI的CSS/USS通过增加CIF域，也部分或全部位于调度所述主小区的调度载波中。
可选的，DCI格式/搜索空间划分模块包括：
候选集数量调节单元，设置为为所述CSS/USS配置调节因子A，调节位于所述主小区和调度所述主小区的调度载波中的候选集数量。
可选的，候选集数量调节单元设置为：
所述主小区中的候选集数量不变，调度所述主小区的调度载波中候选集数量为A*M(L)；或者，所述主小区中候选集数量为A*M(L)，调度所述主小区的 调度载波中候选集数量为M(L)-A*M(L)；或者，调度所述主小区的调度载波中候选集数量为A*M(L)，所述主小区中候选集数量为M(L)-A*M(L)；其中，M(L)为聚合等级L的候选集数量。
本申请实施例各装置中的各模块的功能可以参见上述方法实施例中的对应描述，在此不再赘述。
图3示出一种设备的结构示意图，包括：处理器310和存储器320。该设备中处理器310的数量可以是一个或者多个，图3中以一个处理器310为例。该设备中存储器320的数量可以是一个或者多个，图3中以一个存储器320为例。该设备的处理器310和存储器320可以通过总线或者其他方式连接，图3中以通过总线连接为例。
存储器320作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例的设备对应的程序指令/模块(例如，调度主小区的配置装置中的跨载波调度配置模块)。存储器320可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器320可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器320可包括相对于处理器310远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
上述提供的设备可设置为执行本申请实施例中的任意一种方法。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中的任意一种方法。
术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一 种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (20)

  1. 一种调度主小区的配置方法，包括：
    配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度。
  2. 根据权利要求1所述的方法，其中，在所述载波为主小区的情况下，所述配置载波的跨载波调度配置信息，包括：
    配置所述主小区的调度小区信息为被调度；且配置所述主小区的调度载波索引和配置所述主小区在调度载波中的载波指示域CIF取值。
  3. 根据权利要求1所述的方法，其中，在所述载波为主小区的情况下，所述配置载波的跨载波调度配置信息，包括：
    配置所述主小区的调度小区信息为自调度和被调度；且配置所述主小区是否存在CIF，配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
  4. 根据权利要求1所述的方法，其中，在所述载波为主小区的情况下，所述配置载波的跨载波调度配置信息，包括：
    配置所述主小区的调度小区信息为自调度；且配置所述主小区是否允许被调度，在所述主小区允许被调度的情况下配置所述主小区的调度载波索引和配置所述主小区在调度载波中的CIF取值。
  5. 根据权利要求1所述的方法，其中，在所述载波为辅小区的情况下，所述配置载波的跨载波调度配置信息，包括：
    配置所述辅小区的调度小区信息为自调度；且配置所述辅小区是否允许调度主小区，在所述辅小区允许调度所述主小区的情况下配置所述主小区在所述辅小区中的CIF取值。
  6. 根据权利要求5所述的方法，其中，所述配置所述辅小区是否允许调度主小区，包括：
    通过显示配置所述辅小区允许或不允许调度所述主小区；或，
    通过预设规则确定所述辅小区允许或不允许调度所述主小区。
  7. 根据权利要求6所述的方法，其中，所述预设规则包括：
    在配置了所述主小区在所述辅小区中的CIF取值的情况下，表示所述辅小区允许调度所述主小区，在不配置所述主小区在所述辅小区中的CIF取值的情况下，表示所述辅小区不允许调度所述主小区；或，
    在配置的所述主小区在所述辅小区中的CIF取值为取值集合X中的元素的情况下，表示所述辅小区允许调度所述主小区，在配置的所述主小区在所述辅 小区中的CIF取值为Y且Y不等于取值集合X中的元素的情况下，表示所述辅小区不允许调度所述主小区。
  8. 根据权利要求2所述的方法，其中，在配置所述主小区的调度小区信息为被调度的情况下，所述主小区具有自调度能力。
  9. 根据权利要求8所述的方法，其中，所述主小区具有自调度能力，包括：
    所述主小区具有自调度能力且CIF域不存在；或，
    所述主小区具有自调度能力且CIF域是否存在通过高层信令配置。
  10. 根据权利要求2-4中任一项所述的方法，还包括：
    配置所述主小区的调度载波索引数量为预设数量。
  11. 根据权利要求10所述的方法，其中，所述预设数量为1。
  12. 根据权利要求4所述的方法，其中，所述配置所述主小区是否允许被调度，包括：
    通过显示配置所述主小区允许或不允许被调度；或，
    通过预设规则确定所述主小区允许或不允许被调度。
  13. 根据权利要求12所述的方法，其中，所述预设规则包括以下至少之一：
    在配置了所述主小区在调度载波中的CIF取值的情况下，表示所述主小区允许被调度，在不配置所述主小区在调度载波中的CIF取值的情况下，表示所述主小区不允许被调度；
    在配置了所述主小区的调度载波索引的情况下，表示所述主小区允许被调度，在不配置所述主小区的调度载波索引的情况下，表示所述主小区不允许被调度。
  14. 根据权利要求12所述的方法，其中，所述预设规则包括以下至少之一：
    在配置的所述主小区在调度载波中的CIF取值为取值集合X中的元素的情况下，表示所述主小区允许被调度，在配置的所述主小区在调度载波中的CIF取值为Y且Y不等于取值集合X中的元素的情况下，表示所述主小区不允许被调度；
    在配置的所述主小区的调度载波索引取值为取值集合M中的元素的情况下，表示所述主小区允许被调度，在配置的所述主小区的调度载波索引取值为N且N不等于取值集合M中的元素的情况下，表示所述主小区不允许被调度。
  15. 根据权利要求1-6、8、12中任一项所述的方法，还包括：
    在所述主小区支持自调度和被调度的情况下，调度所述主小区的下行控制信息DCI格式或搜索空间类型通过如下方式之一确定：
    所述主小区上仅配置公共搜索空间CSS和承载fallback DCI的用户设备UE特定的搜索空间USS，承载non-fallback DCI的USS全都位于调度所述主小区的调度载波中；
    所述主小区上配置CSS、承载fallback DCI的USS和承载non-fallback DCI的USS，所述承载non-fallback DCI的USS也全部或部分位于调度所述主小区的调度载波中；
    承载fallback DCI的CSS或USS通过增加CIF域，也部分或全部位于调度所述主小区的调度载波中。
  16. 根据权利要求15所述的方法，其中，所述承载fallback DCI的CSS或USS通过增加CIF域，也部分或全部位于调度所述主小区的调度载波中，包括：
    为所述CSS或USS配置调节因子A，以调节所述CSS或USS位于所述主小区和调度所述主小区的调度载波中的候选集数量。
  17. 根据权利要求16所述的方法，其中，所述为所述CSS或USS配置调节因子A，以调节所述CSS或USS位于所述主小区和调度所述主小区的调度载波中的候选集数量，包括：
    所述主小区中的候选集数量不变，调度所述主小区的调度载波中候选集数量为A*M(L)；或者，
    所述主小区中候选集数量为A*M(L)，调度所述主小区的调度载波中候选集数量为M(L)-A*M(L)；或者，
    调度所述主小区的调度载波中候选集数量为A*M(L)，所述主小区中候选集数量为M(L)-A*M(L)；
    其中，M(L)为所述CSS或USS包含的聚合等级L的候选集数量。
  18. 一种调度主小区的配置装置，包括：
    跨载波调度配置模块，设置为配置载波的跨载波调度配置信息，使得主小区支持自调度和被调度。
  19. 一种设备，包括：存储器，以及至少一个处理器；
    所述存储器，设置为存储至少一个程序；
    当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现如权利要求1-17中任一项所述的调度主小区的配置方法。
  20. 一种存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-17中任一项所述的调度主小区的配置方法。
PCT/CN2021/075190 2020-02-12 2021-02-04 调度主小区的配置方法、装置、设备及储存介质 WO2021160011A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020227030840A KR20220140552A (ko) 2020-02-12 2021-02-04 프라이머리 셀의 스케줄링 구성 방법, 장치, 설비 및 저장 매체
EP21753012.0A EP4106450A4 (en) 2020-02-12 2021-02-04 CONFIGURATION METHOD AND DEVICE FOR PLANNING A PRIMARY CELL, DEVICE AND STORAGE MEDIUM
US17/799,594 US20230084554A1 (en) 2020-02-12 2021-02-04 Configuration method and apparatus for scheduling primary cell, and device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010089243.2A CN111901869A (zh) 2020-02-12 2020-02-12 一种调度主小区的配置方法、装置、设备及储存介质
CN202010089243.2 2020-02-12

Publications (1)

Publication Number Publication Date
WO2021160011A1 true WO2021160011A1 (zh) 2021-08-19

Family

ID=73169699

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/075190 WO2021160011A1 (zh) 2020-02-12 2021-02-04 调度主小区的配置方法、装置、设备及储存介质

Country Status (5)

Country Link
US (1) US20230084554A1 (zh)
EP (1) EP4106450A4 (zh)
KR (1) KR20220140552A (zh)
CN (1) CN111901869A (zh)
WO (1) WO2021160011A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901869A (zh) * 2020-02-12 2020-11-06 中兴通讯股份有限公司 一种调度主小区的配置方法、装置、设备及储存介质
CN113382479B (zh) * 2020-02-25 2023-04-18 维沃移动通信有限公司 服务小区调度方法、终端设备和网络设备
US12108408B2 (en) * 2020-10-01 2024-10-01 Qualcomm Incorporated Providing cross-carrier scheduling control information for a primary cell via both a secondary cell and the primary cell
US20230362943A1 (en) * 2021-01-15 2023-11-09 Apple Inc. Scheduling restriction enhancement for lte and nr dss
CN115119212A (zh) * 2021-03-17 2022-09-27 中兴通讯股份有限公司 一种频谱共享信道资源分配方法、系统和电子设备
CN115134916A (zh) * 2021-03-25 2022-09-30 维沃移动通信有限公司 传输处理方法及相关设备
CN116472764A (zh) * 2021-03-30 2023-07-21 Oppo广东移动通信有限公司 搜索空间配置方法、装置、设备及存储介质
CN115334581A (zh) * 2021-05-11 2022-11-11 维沃移动通信有限公司 控制资源分配方法、装置及通信设备
CN116033570A (zh) * 2021-10-22 2023-04-28 华为技术有限公司 通信方法及装置
CN116095853A (zh) * 2021-11-05 2023-05-09 华为技术有限公司 一种通信方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105991263A (zh) * 2015-01-30 2016-10-05 中兴通讯股份有限公司 下行控制信息dci的配置、下行数据的接收方法及装置
US20180167957A1 (en) * 2015-08-12 2018-06-14 Wilus Institute Of Standards And Technology Inc. Method, apparatus, and system for transmitting control channel in unlicensed band
CN110662228A (zh) * 2018-06-29 2020-01-07 维沃移动通信有限公司 跨载波调度的pdcch候选分配方法和设备
CN111901869A (zh) * 2020-02-12 2020-11-06 中兴通讯股份有限公司 一种调度主小区的配置方法、装置、设备及储存介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103875201B (zh) * 2011-09-30 2017-02-15 Lg电子株式会社 在无线通信系统中传送信道状态信息的方法和设备
WO2016119882A1 (en) * 2015-01-30 2016-08-04 Nokia Solutions And Networks Oy Carrier aggregation with cross-carrier scheduling
CN111132344B (zh) * 2019-12-27 2023-01-17 北京紫光展锐通信技术有限公司 跨载波调度方法、装置及存储介质
CN113225817B (zh) * 2020-02-06 2023-04-07 维沃移动通信有限公司 调度方法、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105991263A (zh) * 2015-01-30 2016-10-05 中兴通讯股份有限公司 下行控制信息dci的配置、下行数据的接收方法及装置
US20180167957A1 (en) * 2015-08-12 2018-06-14 Wilus Institute Of Standards And Technology Inc. Method, apparatus, and system for transmitting control channel in unlicensed band
CN110662228A (zh) * 2018-06-29 2020-01-07 维沃移动通信有限公司 跨载波调度的pdcch候选分配方法和设备
CN111901869A (zh) * 2020-02-12 2020-11-06 中兴通讯股份有限公司 一种调度主小区的配置方法、装置、设备及储存介质

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.7.0, 27 September 2019 (2019-09-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 527, XP051785033 *
ERICSSON (MODERATOR): "Summary of Rel-17 email discussion on NR dynamic spectrum sharing", 3GPP DRAFT; RP-192677, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Sitges, Spain; 20191209 - 20191212, 2 December 2019 (2019-12-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051834283 *
ERICSSON: "New WID on NR Dynamic spectrum sharing (DSS)", 3GPP DRAFT; RP-193260, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Sitges, Spain; 20191209 - 20191212, 12 December 2019 (2019-12-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051840390 *
HUAWEI, HISILICON: "NR CA enhancements and DSS", 3GPP DRAFT; RP-192797, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Sitges, Spain; 20191209 - 20191212, 2 December 2019 (2019-12-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051834390 *
See also references of EP4106450A4

Also Published As

Publication number Publication date
EP4106450A1 (en) 2022-12-21
CN111901869A (zh) 2020-11-06
EP4106450A4 (en) 2024-03-27
US20230084554A1 (en) 2023-03-16
KR20220140552A (ko) 2022-10-18

Similar Documents

Publication Publication Date Title
WO2021160011A1 (zh) 调度主小区的配置方法、装置、设备及储存介质
JP6928109B2 (ja) フレキシブルスロットフォーマットインジケータを利用するための装置、システム、及び方法
TWI688296B (zh) 確定資源配置、指示資源配置的方法、終端及網路側設備
EP2702735B1 (en) Method for communicating control information using carrier aggregation
US11012220B2 (en) Allocation of communication resources for control signals in the uplink
KR101298912B1 (ko) 업링크 캐리어들을 우선순위 매기기 위한 방법들, 장치들, 및 컴퓨터 프로그램 물건들
CN110620645B (zh) 信息确定、调整方法、门限值使用方法、终端及存储介质
US20220408473A1 (en) Serving cell scheduling method, terminal device, and network device
WO2019056164A1 (en) METHODS AND APPARATUS FOR TRANSMITTING CONTROL INFORMATION
US11985686B2 (en) Channel resource indication method, terminal device and network device
CN107113836B (zh) 无线通信中的调度增强
BR112018003513B1 (pt) Método, aparelho, sistema e meio legível por computador para configurar subquadro em sistema de celular
JP7066624B2 (ja) ユーザ装置及び上り信号送信方法
JP7162080B2 (ja) 超高信頼低遅延通信の設定
KR102357331B1 (ko) 데이터 송신을 위한 제어 리소스들의 사용에 관하여
WO2018083868A1 (ja) ユーザ装置及び上り信号送信方法
KR20230005216A (ko) 무선 통신에서의 자원 결정
EP4090098A1 (en) Method and device for carrier scheduling
CN114071747A (zh) 信息确定方法、信息发送方法及终端
WO2015139582A1 (zh) 一种ue、基站中非授权频谱上的通信方法和设备
WO2022029983A1 (ja) 端末、基地局装置、及び受信方法
CN104604308A (zh) 功率控制
WO2024027562A1 (zh) 信道检测方法、装置、终端、网络设备及存储介质
US20240080167A1 (en) Method for uplink transmission, terminal device, and network device
WO2018171347A1 (zh) 一种解调导频的处理方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21753012

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227030840

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021753012

Country of ref document: EP

Effective date: 20220912