Frequency domain resource allocation method and device

By optimizing the frequency domain resource allocation method and utilizing the index of the frequency domain resource allocation bitmap or set, the problem of high overhead in the frequency domain resource allocation domain in the new air interface system is solved, thereby saving control channel resources and improving demodulation performance.

CN113630874BActive Publication Date: 2024-11-12VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010383541.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-05-08
Publication Date
2024-11-12
Estimated Expiration
2040-05-08

AI Technical Summary

Technical Problem

In new air interface systems, the overhead of frequency domain resource allocation is large, resulting in an excessively large downlink control information (DCI) size. Especially in multi-carrier, cell, or bandwidth-limited scenarios, existing technologies struggle to effectively reduce control channel resource overhead.

Method used

By using the frequency domain resource allocation method for receiving and transmitting, and by utilizing the index of the frequency domain resource allocation bitmap or set, combined with preset conditions, the frequency domain resource allocation process is optimized, reducing the number of bits and overhead of the frequency domain resource allocation domain, and improving the demodulation performance of the control channel and the system coverage.

Benefits of technology

While maintaining scheduling flexibility, it reduces control channel resource overhead and improves the demodulation performance of the control channel and the effective coverage of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113630874B_ABST
    Figure CN113630874B_ABST
Patent Text Reader

Abstract

An embodiment of the present invention provides a frequency domain resource allocation method and device, the method comprising: receiving first downlink control information for scheduling multiple carriers, cells or bandwidth parts; obtaining the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts according to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit, which can reduce the control channel resource overhead and improve the demodulation performance of the control channel and the effective coverage range of the system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technology, and in particular to a frequency domain resource allocation method and device. Background Art

[0002] The current New Radio (NR) system does not support scheduling multiple carriers in one downlink control information (DCI). In the dynamic spectrum sharing (DSS) scenario, supporting one DCI scheduling multiple carriers can effectively reduce the redundancy (overhead) of the physical downlink control channel (PDCCH).

[0003] However, in a scenario where a DCI schedules multiple carriers, cells or bandwidth parts (Band Width Part, BWP), the number of bits required for frequency domain resource allocation is large. If multiple carriers, cells or BWPs use their own frequency domain resource allocation domains, the frequency domain resource allocation domain overhead is large and may cause the final DCI size to be too large. Summary of the invention

[0004] An object of an embodiment of the present invention is to provide a method and device for allocating frequency domain resources to solve the problem of large domain overhead of frequency domain resource allocation.

[0005] In a first aspect, an embodiment of the present invention provides a frequency domain resource allocation method, which is applied to a terminal, including:

[0006] Receiving first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0007] According to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit, the frequency domain resources of the terminal on multiple carriers, cells or bandwidth parts are obtained.

[0008] In a second aspect, an embodiment of the present invention provides a frequency domain resource allocation method, which is applied to a network device, including:

[0009] Sending first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0010] Among them, the first downlink control information is used to indicate the terminal, based on the first downlink control information, the number of bits required for the frequency domain resource allocation of each carrier, cell or bandwidth part scheduled and the frequency domain resource group corresponding to each bit, to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts.

[0011] In a third aspect, an embodiment of the present invention provides a frequency domain resource allocation method, applied to a terminal, including:

[0012] receiving second downlink control information for scheduling a plurality of carriers, cells or bandwidth parts;

[0013] Obtaining frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts according to the frequency domain resource allocation field in the second downlink control information;

[0014] The frequency domain resource allocation domain includes: an index corresponding to a frequency domain resource allocation bitmap, or an index corresponding to a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0015] In a fourth aspect, an embodiment of the present invention provides a frequency domain resource allocation method, which is applied to a network device, including:

[0016] Sending second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0017] The frequency domain resource allocation field of the second downlink control information includes: an index corresponding to a frequency domain resource allocation bitmap, or an index corresponding to a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0018] In a fifth aspect, an embodiment of the present invention provides a terminal, including:

[0019] A first receiving module, configured to receive first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0020] The first processing module is used to obtain the frequency domain resources of the terminal on multiple carriers, cells or bandwidth parts according to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit.

[0021] Optionally, the terminal further includes: a second processing module, configured to determine the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts;

[0022] The third processing module is used to obtain the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

[0023] Optionally, the frequency domain resource group sizes of multiple carriers, cells or bandwidth parts are configured on the network side.

[0024] Optionally, the second processing module is further used to: obtain the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity;

[0025] The first quantity includes any one of the following:

[0026] The total number of frequency domain resources of the multiple carriers;

[0027] The total number of frequency domain resources of the multiple cells;

[0028] The total number of frequency domain resources of the plurality of bandwidth parts;

[0029] a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers;

[0030] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells;

[0031] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

[0032] Optionally, the terminal further includes:

[0033] A fourth processing module, configured to obtain a frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the number of frequency domain resources of each scheduled carrier, cell or bandwidth part;

[0034] A fifth processing module, configured to perform scaling processing on the frequency domain resource group size of each scheduled carrier, cell or bandwidth part;

[0035] The sixth processing module is used to obtain the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the scaled frequency domain resource group size of each scheduled carrier, cell or bandwidth part.

[0036] Optionally, the fifth processing module is further used to: perform scaling processing on the frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the scaling factor;

[0037] The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

[0038] Optionally, the size of the frequency domain resource allocation indication field of the first downlink control information is: ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

[0039] Optionally, the frequency domain resources of the terminal on the multiple carriers or cells or bandwidth parts include any one of the following:

[0040] frequency domain resources jointly allocated to the terminal on the multiple carriers;

[0041] frequency domain resources jointly allocated to the terminal on the multiple cells;

[0042] jointly allocating frequency domain resources for the terminal over the plurality of bandwidth portions;

[0043] frequency domain resources allocated to the terminal by each carrier in the multiple carriers;

[0044] frequency domain resources allocated to the terminal by each cell in the multiple cells;

[0045] Each bandwidth part in the multiple bandwidth parts is a frequency domain resource allocated to the terminal.

[0046] In a sixth aspect, an embodiment of the present invention provides a network device, including:

[0047] A first sending module, used for sending first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0048] Among them, the first downlink control information is used to indicate the terminal, based on the first downlink control information, the number of bits required for the frequency domain resource allocation of each carrier, cell or bandwidth part scheduled and the frequency domain resource group corresponding to each bit, to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts.

[0049] Optionally, the network device further includes:

[0050] The determination module is used to determine the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit.

[0051] Optionally, the network device further includes:

[0052] An eighth processing module, configured to determine a frequency domain resource group size for the plurality of carriers, cells or bandwidth portions;

[0053] The ninth processing module is used to obtain the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

[0054] Optionally, the eighth processing module is further used to: obtain the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity;

[0055] The first quantity includes any one of the following:

[0056] The total number of frequency domain resources of the multiple carriers;

[0057] The total number of frequency domain resources of the multiple cells;

[0058] The total number of frequency domain resources of the plurality of bandwidth parts;

[0059] a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers;

[0060] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells;

[0061] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

[0062] Optionally, the network device further includes:

[0063] A tenth processing module, configured to obtain a frequency domain resource group size of each carrier, cell or bandwidth part according to the number of frequency domain resources of each carrier, cell or bandwidth part being scheduled;

[0064] An eleventh processing module is used to scale the frequency domain resource group size of each scheduled carrier, cell or bandwidth part;

[0065] The twelfth processing module is used to obtain the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the scaled frequency domain resource group size of the carrier, cell or bandwidth part.

[0066] Optionally, the eleventh processing module is further used to: perform scaling processing on the frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the scaling factor;

[0067] The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

[0068] Optionally, the size of the frequency domain resource allocation indication field of the first downlink control information is: ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

[0069] In a seventh aspect, an embodiment of the present invention provides a terminal, including:

[0070] A second receiving module, configured to receive second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0071] A thirteenth processing module, configured to obtain frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts according to the frequency domain resource allocation domain in the second downlink control information;

[0072] The frequency domain resource allocation domain includes: an index of a frequency domain resource allocation bitmap, or an index of a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0073] Optionally, the terminal further includes:

[0074] The third receiving module is used to receive a list of resource indication values ​​configured by the network device for each scheduled carrier, cell or bandwidth part, wherein the index represents the position of the frequency domain resource allocation bitmap in the resource indication value list, or to receive a list of resource indication values ​​jointly configured by the network device for multiple carriers, cells or bandwidth parts, wherein the index represents the position of the frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0075] Optionally, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each carrier, cell or bandwidth part, or the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0076] Optionally, the frequency domain resource allocation bitmap indicates frequency domain resources allocated to the terminal in one carrier, cell or bandwidth part, or indicates frequency domain resources jointly allocated to the terminal in multiple carriers, cells or bandwidth parts.

[0077] Optionally, the preset condition includes one or more of the following:

[0078] The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value;

[0079] The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value;

[0080] The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0081] Optionally, the size of the frequency domain resource allocation domain is related to the number of the frequency domain resource sets.

[0082] Optionally, the index of the frequency domain resource set represents the order in which the frequency domain resource set is arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0083] In an eighth aspect, an embodiment of the present invention provides a network device, including:

[0084] A second sending module, used for sending second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0085] The frequency domain resource allocation field of the second downlink control information includes: an index of a frequency domain resource allocation bitmap, or an index of a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0086] Optionally, the network device further includes:

[0087] The third sending module is used to send a list of resource indication values ​​configured for each scheduled carrier, cell or bandwidth part, and the index represents the position of the frequency domain resource allocation bitmap in the resource indication value list, or to send a list of resource indication values ​​jointly configured for multiple carriers, cells or bandwidth parts, and the index represents the position of the frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0088] Optionally, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each carrier, cell or bandwidth part, or the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0089] Optionally, the preset condition includes one or more of the following:

[0090] The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value;

[0091] The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value;

[0092] The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0093] Optionally, the size of the frequency domain resource allocation domain is related to the number of the frequency domain resource sets.

[0094] Optionally, the index of the frequency domain resource set represents the order in which the frequency domain resource set is arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0095] In the ninth aspect, an embodiment of the present invention provides a communication device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the frequency domain resource allocation method as described in the first aspect, the second aspect, or the third aspect are implemented.

[0096] In the tenth aspect, an embodiment of the present invention provides a readable storage medium, characterized in that a program is stored on the readable storage medium, and when the program is executed by a processor, the steps of the frequency domain resource allocation method described in the first aspect, the second aspect or the third aspect are implemented.

[0097] In the eleventh aspect, an embodiment of the present invention provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, the second aspect, or the third aspect.

[0098] In the embodiment of the present invention, the control channel resource overhead can be reduced, and the demodulation performance of the control channel and the effective coverage of the system can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] By reading the detailed description of the following embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The accompanying drawings are only used to illustrate the purpose of the preferred embodiments and are not considered to be limitations of the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings.

[0100] In the attached picture:

[0101] Figure 1 A schematic diagram of the architecture of a wireless communication system according to an embodiment of the present invention;

[0102] Figure 2 This is one of the flow charts of the frequency domain resource allocation method according to an embodiment of the present invention;

[0103] Figure 3 This is a second flowchart of the frequency domain resource allocation method according to an embodiment of the present invention;

[0104] Figure 4 This is a third flowchart of the frequency domain resource allocation method according to an embodiment of the present invention;

[0105] Figure 5 This is a fourth flowchart of the frequency domain resource allocation method according to an embodiment of the present invention;

[0106] Figure 6is one of the schematic diagrams of a terminal according to an embodiment of the present invention;

[0107] Figure 7 This is one of the schematic diagrams of a network device according to an embodiment of the present invention;

[0108] Figure 8 This is a second schematic diagram of a terminal according to an embodiment of the present invention;

[0109] Fig. 9 This is a second schematic diagram of a network device according to an embodiment of the present invention;

[0110] Fig.10 Schematic diagram of a communication device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0111] In order to facilitate understanding of the embodiments of the present invention, the following technical points are first introduced:

[0112] (1) Downlink frequency domain resource allocation in NR:

[0113] In NR, there are two types of resource blocks (RBs), including physical resource blocks (PRBs) and virtual resource blocks (VRBs). The frequency domain resources of the downlink physical downlink shared channel (PDSCH) are VRBs and PRBs are numbered from 0 to In PDSCH resource allocation, there are two VRB to PRB mapping modes: non-interleaved and interleaved.

[0114] The frequency domain resource allocation of PDSCH in NR is indicated by the frequency domain resource allocation (FDRA) field of DCI, that is, the index value of the VRB of PDSCH in the downlink BWP.

[0115] Two resource allocation types are supported: Type 0 (non-contiguous frequency domain resource allocation) and Type 1 (contiguous frequency domain resource allocation).

[0116] DCI 1_0 only supports the frequency domain resource allocation type of Type 1, and there is 1 bit indicating the mapping method from VRB to PRB.

[0117] For DCI 1_1, which can support frequency domain resource allocation types of Type 0 or Type 1, the high-level configuration can be Type 0 or Type 1, or the high-level configuration can be configured as Dynamic Switch mode and the resource allocation type is indicated by the high 1 bit of the FDRA field in DCI 1_1. If the high-level configuration does not support the interleaving mode of VRB to PRB mapping, or the high-level configuration only supports the Type 0 resource allocation type, DCI 1_1 is non-interleaved VRB to PRB mapping, and there is no VRB to PRB mapping indication bit. Otherwise, the non-interleaved or interleaved mode is indicated by the VRB to PRB mapping bit.

[0118] The resource allocation methods for Type 0 and Type 1 are shown in the uplink and downlink frequency domain resource allocation schemes in the following NR.

[0119] (2) Introduction to two resource allocation types: Type 0 and Type 1:

[0120] Type0:

[0121] The resource blocks in the target uplink / downlink BWP for resource allocation are divided into multiple resource block groups (RBGs), each RBG corresponds to a set of up to P consecutive VRBs, where P is based on a high-level parameter configuration (indicating which column in Table 1 is used, Configuration 1 or Configuration 2), and the number of resource blocks contained in the target uplink / downlink BWP.

[0122] Table 1: Nominal RBG size P

[0123]

[0124] The FDRA field of DCI Format 0_1 / 1_1 uses a bitmap to indicate whether each RBG in the target uplink BWP is allocated to the terminal. Each bit in the bitmap corresponds to each RBG in the target uplink / downlink BWP. When a bit in the bitmap is set to 1, it indicates that the corresponding RBG is allocated to the terminal, that is, all resource blocks contained in this RBG are allocated to the terminal.

[0125] DCI Format 0_0 / 1_0 does not support uplink resource allocation type 0.

[0126] Type 1

[0127] Assume that the starting VRB number in the VRB set is RB start (Local number within the target uplink BWP), the number of consecutively allocated VRBs is L RBs , the Resource Indication Value (RIV) is calculated based on the following formula:

[0128] if but

[0129] otherwise,

[0130] Above is the number of VRBs included in the target uplink BWP, L RBs ≥1 and cannot exceed

[0131] The RIV is indicated in the "FDRA" field of DCI Format 0_0 / 0_1 / 1_0 / 1_1, thereby indicating the allocated VRB set to the terminal.

[0132] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0133] The term "comprise" and any variation thereof in the specification and claims of the present application are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, such as A and / or B, means that A alone, B alone, and A and B exist in three cases.

[0134] In the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present invention should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0135] The technology described in this article is not limited to Long Time Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems.

[0136] The terms "system" and "network" are often used interchangeably. A CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system may implement radio technologies such as Global System for Mobile Communication (GSM). An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are new UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies.

[0137] The following describes an embodiment of the present invention in conjunction with the accompanying drawings. A frequency domain resource allocation method and device provided by the embodiment of the present invention can be applied to a wireless communication system. Figure 1 , is a schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present invention. Figure 1 As shown, the wireless communication system may include: a network device 11 and a terminal 12, the terminal 12 may be denoted as UE12, and the terminal 12 may communicate with the network device 11 (transmit signaling or transmit data). In practical applications, the connection between the above-mentioned devices may be a wireless connection. In order to conveniently and intuitively represent the connection relationship between the devices, Figure 1 Solid lines are used to indicate.

[0138] The network device 11 provided in an embodiment of the present invention may be a base station, which may be a commonly used base station, an evolved node base station (eNB), or a network device in a 5G system (for example, a next generation node base station (gNB) or a transmission and reception point (TRP)).

[0139] The terminal 12 provided in the embodiment of the present invention can be a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook or a personal digital assistant (PDA), a mobile Internet device (MID), a wearable device (Wearable Device) or a vehicle-mounted device, etc.

[0140] See also Figure 2 The embodiment of the present invention further provides a frequency domain resource allocation method, the execution subject of the method is a terminal, and includes: step 201 and step 202.

[0141] Step 201: receiving first downlink control information for scheduling multiple carriers, cells or bandwidth parts (or called activated BWP);

[0142] Step 202: According to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit, obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts.

[0143] It should be noted that in the following example, the frequency domain resource is RB, the frequency domain resource group is RBG, and the frequency domain resource group size is RBG size, but it is not limited to this.

[0144] For example, the RBG size is determined according to the total number of RBs of multiple carriers, cells or BWPs scheduled by the first DCI, or according to the number of RBs of each carrier, cell or BWP, and Type 0 frequency domain resource allocation indication is performed for each carrier, cell or BWP according to the RBG size, or Type 0 frequency domain resource allocation is jointly indicated for multiple carriers, cells or BWPs.

[0145] In some embodiments, before step 202, Figure 2The method shown may also include: determining the frequency domain resource group size of the multiple carriers, cells or bandwidth parts; and obtaining the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit based on the frequency domain resource group size.

[0146] Further, the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts are configured by the network side; or, the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts are obtained according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity;

[0147] Wherein, the first quantity includes one or more of the following:

[0148] (1) The total number of frequency domain resources of multiple carriers;

[0149] The total number of frequency domain resources of multiple carriers refers to the sum of the number of frequency domain resources of each carrier.

[0150] (2) The total number of frequency domain resources in multiple cells;

[0151] The total number of frequency domain resources of multiple cells refers to the sum of the number of frequency domain resources of each cell.

[0152] (3) the total number of frequency domain resources in multiple bandwidth parts;

[0153] The total number of frequency domain resources of multiple bandwidth parts refers to the sum of the number of frequency domain resources of each bandwidth part.

[0154] (4) a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers;

[0155] (5) the maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells;

[0156] (6) A maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

[0157] The following combines solutions 1 to 3 to introduce how the terminal can reduce the Type 0 frequency domain resource allocation overhead in the scenario where a DCI schedules multiple carriers, cells, or BWPs:

[0158] Solution 1: According to the total number of RBs of multiple carriers, cells or activated BWPs scheduled by the first DCI, or the maximum / minimum number of RBs among N carriers, cells or activated BWPs, and the correspondence between the number of RBs and the RBG size (it should be noted that this correspondence is different from the correspondence for scheduling a single carrier, for example, a new RB size range or a new RBG size is introduced), the RBG size P (the number of RBs included) is determined as the granularity for indicating the frequency domain resource allocation for each carrier, cell or activated BWP (i.e., the number of RBs represented by 1 bit in the bitmap), and the number of bits required for the frequency domain resource allocation of each carrier, cell or activated BWP and / or the frequency domain resource group corresponding to each bit is calculated.

[0159] At this time, the size of the frequency domain resource allocation indication field is ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the RBG size P in the i-th carrier, cell or activated BWP, and i is a natural number.

[0160] It can be understood that the above RBG size P can be configured on the network side, for example, through Radio Resource Control (RRC) configuration.

[0161] Solution 2: Determine the RBG size of each carrier, cell or activated BWP according to the number of RBs of each carrier, cell or activated BWP scheduled by the first DCI, scale the determined RBG size according to a predefined or RRC configured scaling factor, or according to the number of carriers, cells or activated BWPs scheduled by the first DCI, and use it as the granularity for indicating frequency domain resource allocation for each carrier or activated BWP (i.e., the number of RBs represented by 1 bit in the bitmap), and calculate the number of bits required for frequency domain resource allocation of each carrier, cell or activated BWP and / or the frequency domain resource group corresponding to each bit.

[0162] At this time, the size of the frequency domain resource allocation indication field is ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the RBG size P in the i-th carrier, cell or activated BWP, and i is a natural number.

[0163] In some embodiments of Scheme 2, before step 202, Figure 2 The method shown may also include:

[0164] According to the number of frequency domain resources of each scheduled carrier, cell or bandwidth part, the size of the frequency domain resource group of each scheduled carrier, cell or bandwidth part is obtained; the size of the frequency domain resource group of each scheduled carrier, cell or bandwidth part is scaled; according to the scaled size of the frequency domain resource group of each scheduled carrier, cell or bandwidth part, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit are obtained.

[0165] Solution 3: Determine the RBG size based on the total number of RBs of multiple carriers, cells or activated BWPs scheduled by the first DCI or the maximum or minimum number of RBs among N (N greater than or equal to 1) carriers, and the correspondence between the number of RBs and the RBG size (it should be noted that this correspondence is different from the correspondence for scheduling a single carrier, for example, a new RB size range or a new RBG size is introduced), and then a joint Type 0 frequency domain resource allocation indication is performed for multiple carriers, cells or BWPs according to the RBG size, for example, continuous fragmented RBGs located on two BWPs share 1 bit for indication.

[0166] It can be understood that the above RBG size can be configured on the network side, for example, through RRC configuration.

[0167] In some implementations, the Type 0 frequency domain resources allocated to the terminal in the multiple carriers or cells or bandwidth parts include any one of the following:

[0168] (1) Type 0 frequency domain resources jointly allocated to the terminal on the multiple carriers;

[0169] (2) Type 0 frequency domain resources jointly allocated to the terminal on the multiple cells;

[0170] (3) Type 0 frequency domain resources jointly allocated to the terminal on the multiple bandwidth parts;

[0171] (4) Type 0 frequency domain resources allocated to the terminal by each carrier in the multiple carriers;

[0172] (5) Type 0 frequency domain resources allocated to the terminal by each of the multiple cells;

[0173] (6) Type 0 frequency domain resources allocated to the terminal in each bandwidth part among the multiple bandwidth parts.

[0174] In the embodiment of the present invention, in a scenario where a DCI schedules multiple carriers, cells or BWPs, it is possible to reduce control channel resource overhead and improve the demodulation performance of the control channel and the effective coverage of the system while maintaining the same scheduling flexibility.

[0175] See also Figure 3 The embodiment of the present invention further provides a frequency domain resource allocation method, the execution subject of the method may be a network device, including: step 301.

[0176] Step 301: Sending first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0177] Among them, the first downlink control information is used to indicate the terminal, based on the first downlink control information, the number of bits required for the frequency domain resource allocation of each carrier, cell or bandwidth part scheduled and the frequency domain resource group corresponding to each bit, to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts.

[0178] In some embodiments, before step 301, Figure 3 The method shown may also include:

[0179] Determine the number of bits required for frequency domain resource allocation of each carrier, cell or bandwidth part to be scheduled and the frequency domain resource group corresponding to each bit.

[0180] In some embodiments, before step 301, Figure 3 The method shown may also include: determining the frequency domain resource group size of the multiple carriers, cells or bandwidth parts; and obtaining the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit based on the frequency domain resource group size.

[0181] For example, the network device configures the frequency domain resource sizes of multiple carriers, cells or bandwidth parts through RRC, and determines the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit based on the frequency domain resource size.

[0182] Alternatively, the network device obtains the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the first quantity and the correspondence between the number of frequency domain resources and the frequency domain resource group size;

[0183] Wherein, the first quantity includes one or more of the following:

[0184] The following combines solutions 1 to 3 to introduce how network devices can reduce Type 0 frequency domain resource allocation overhead when a DCI schedules multiple carriers, cells, or BWPs:

[0185] Solution 1: According to the total number of RBs of multiple carriers, cells or activated BWPs scheduled by the first DCI, or the maximum / minimum number of RBs among N carriers, cells or activated BWPs, and the correspondence between the number of RBs and the RBG size (it should be noted that this correspondence is different from the correspondence for scheduling a single carrier, for example, a new RB size range or a new RBG size is introduced), the RBG size P (the number of RBs included) is determined as the granularity for indicating the frequency domain resource allocation for each carrier, cell or activated BWP (i.e., the number of RBs represented by 1 bit in the bitmap), and the number of bits required for the frequency domain resource allocation of each carrier, cell or activated BWP and / or the frequency domain resource group corresponding to each bit is calculated.

[0186] At this time, the size of the frequency domain resource allocation indication field is ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the RBG size P in the i-th carrier, cell or activated BWP, and i is a natural number.

[0187] It can be understood that the above RBG size P can be configured on the network side, for example, through Radio Resource Control (RRC) configuration.

[0188] Solution 2: Determine the RBG size of each carrier, cell or activated BWP according to the number of RBs of each carrier, cell or activated BWP scheduled by the first DCI, scale the determined RBG size according to a predefined or RRC configured scaling factor, or according to the number of carriers, cells or activated BWPs scheduled by the first DCI, and use it as the granularity for indicating frequency domain resource allocation for each carrier or activated BWP (i.e., the number of RBs represented by 1 bit in the bitmap), and calculate the number of bits required for frequency domain resource allocation of each carrier, cell or activated BWP and / or the frequency domain resource group corresponding to each bit.

[0189] At this time, the size of the frequency domain resource allocation indication field is ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the RBG size P in the i-th carrier, cell or activated BWP, and i is a natural number.

[0190] In some embodiments of Scheme 2, before step 301, Figure 3 The method shown may also include:

[0191] According to the number of frequency domain resources of a carrier, a cell or a bandwidth part, the size of the frequency domain resource group of the carrier, the cell or the bandwidth part is obtained; the size of the frequency domain resource group of the carrier, the cell or the bandwidth part is scaled; according to the scaled size of the frequency domain resource group of the carrier, the cell or the bandwidth part, the number of bits required for the frequency domain resource allocation of the carrier, the cell or the bandwidth part and / or the frequency domain resource group corresponding to each bit are obtained.

[0192] Solution 3: Determine the RBG size based on the total number of RBs of multiple carriers, cells or activated BWPs scheduled by the first DCI or the maximum or minimum number of RBs among N (N greater than or equal to 1) carriers, and the correspondence between the number of RBs and the RBG size (it should be noted that this correspondence is different from the correspondence for scheduling a single carrier, for example, a new RB size range or a new RBG size is introduced), and then a joint Type 0 frequency domain resource allocation indication is performed for multiple carriers, cells or BWPs according to the RBG size, for example, continuous fragmented RBGs located on two BWPs share 1 bit for indication.

[0193] It can be understood that the above RBG size can be configured on the network side, for example, through RRC configuration.

[0194] In some implementations, the first downlink control information is used to indicate any one of the following:

[0195] Type 0 frequency domain resources jointly allocated to the terminal on the multiple carriers;

[0196] Type 0 frequency domain resources jointly allocated to the terminal on the multiple cells;

[0197] Type 0 frequency domain resources jointly allocated to the terminal on the multiple bandwidth parts;

[0198] Type 0 frequency domain resources allocated to the terminal by each carrier in the multiple carriers;

[0199] Type 0 frequency domain resources allocated by each cell in the multiple cells to the terminal;

[0200] Each bandwidth part in the multiple bandwidth parts is a Type 0 frequency domain resource allocated to the terminal.

[0201] In the embodiment of the present invention, in a scenario where a DCI schedules multiple carriers, cells or BWPs, it is possible to reduce control channel resource overhead and improve the demodulation performance of the control channel and the effective coverage of the system while maintaining the same scheduling flexibility.

[0202] See also Figure 4 The embodiment of the present invention further provides a frequency domain resource allocation method, the execution subject of the method is a terminal, and the specific steps include: step 401 and step 402.

[0203] Step 401: receiving second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0204] Step 402: Obtain frequency domain resources of the terminal on multiple carriers, cells or bandwidth parts according to the frequency domain resource allocation field in the second downlink control information;

[0205] The frequency domain resource allocation domain includes: an index corresponding to a frequency domain resource allocation bitmap, or an index of a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0206] Solution a: The frequency domain resource allocation domain includes: an index corresponding to the frequency domain resource allocation bitmap.

[0207] In some embodiments of scheme a, the method comprises:

[0208] A resource indication value list configured by a receiving network device for each scheduled carrier, cell or bandwidth part, wherein the index represents the position of the frequency domain resource allocation bitmap in the resource indication value list. It is understood that the index may be implicitly included, and a RIV list is configured, and the position of the frequency domain resource allocation bitmap in the RIV list is the index.

[0209] In some implementations of solution a, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each scheduled carrier, cell or bandwidth part.

[0210] In some embodiments of scheme a, the method comprises:

[0211] A resource indication value list jointly configured by a network device for multiple carriers, cells or bandwidth parts is received, and the index represents a position of a frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0212] In some implementations of solution a, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0213] In some implementations of scheme a, the frequency domain resource allocation bitmap indicates the frequency domain resources allocated to the terminal in a scheduled carrier, cell or bandwidth part, or indicates the frequency domain resources jointly allocated to the terminal in multiple carriers, cells or bandwidth parts.

[0214] That is, in scheme a, RRC configures the RIV list corresponding to the required bitmap code point, and DCI indicates the frequency domain resources through the index corresponding to the bitmap code point;

[0215] (1) If a separate RRC configuration RIV list is performed for one or more scheduled carriers, cells or BWPs, the size of the FDRA field required for scheduling each carrier, cell or BWP is calculated based on the number of bitmap code points of each configured RIV list;

[0216] (2) If a joint RRC configuration RIV list is performed for multiple scheduled carriers, cells or BWPs, the size of the FDRA field required for scheduling the multiple carriers, cells or BWPs is calculated according to the number of code points in the joint configuration RIV list.

[0217] Solution b: an index of a frequency domain resource set, where the frequency domain set meets a preset condition.

[0218] In some implementations of scheme b, the preset conditions include one or more of the following:

[0219] (1) The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value, for example, the first preset value may be predefined or RRC configured;

[0220] (2) The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value, for example, the second preset value may be predefined or RRC configured, such as 50%;

[0221] (3) The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0222] In some implementations of scheme b, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource sets, that is, the number of bits of the frequency domain resource allocation domain required for the carrier, cell or BWP is calculated according to the number of RB sets that meet preset conditions.

[0223] In some implementations of solution b, the index represents the order in which the frequency domain resource sets are arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0224] That is to say, in scheme b, the size of the frequency domain resource allocation domain is determined by the number of frequency domain resource allocation bitmaps that meet the preset conditions, and the frequency domain resource allocation bitmaps that meet the preset conditions are numbered to obtain the index of the bitmap, and the index in the DCI received by the terminal corresponds to the corresponding frequency domain resource allocation bitmap, and the frequency domain resources allocated to multiple carriers, cells or bandwidth parts are obtained. That is, the mapping relationship of index->bitmap->frequency domain resources is specified by the protocol, and both the terminal and the network use this mapping relationship to receive DCI to obtain the frequency domain resources allocated to multiple carriers, cells or bandwidth parts, or send DCI to schedule the corresponding frequency domain resources of multiple carriers, cells or bandwidth parts.

[0225] In an embodiment of the present invention, by reasonably limiting the candidates for frequency domain resource allocation, in a scenario where a DCI schedules multiple carriers, cells or BWPs, it is possible to reduce the control channel resource overhead while maintaining the same scheduling flexibility, thereby improving the demodulation performance of the control channel and the effective coverage of the system.

[0226] See also Figure 5 The embodiment of the present invention further provides a frequency domain resource allocation method, the execution subject of the method is a network device, and the specific steps include: Step 501.

[0227] Step 501: Sending second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0228] The frequency domain resource allocation field in the second downlink control information includes: an index of a frequency domain resource allocation bitmap, or an index of a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0229] Solution a: The frequency domain resource allocation field includes: an index of a frequency domain resource allocation bitmap.

[0230] In some implementations of scheme a, the method further includes: sending a resource indication value list configured for each carrier, cell or bandwidth portion, and the index represents a position of the frequency domain resource allocation bitmap in the resource indication value list.

[0231] In some implementations of solution a, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each carrier, cell or bandwidth part.

[0232] In some other implementations of scheme a, the method further includes: sending a resource indication value list jointly configured for multiple carriers, cells or bandwidth parts, and the index represents the position of the frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0233] In some other implementations of solution a, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0234] In some implementations of scheme a, the frequency domain resource allocation bitmap indicates the frequency domain resources allocated to the terminal in one carrier, cell or bandwidth part, or indicates the frequency domain resources jointly allocated to the terminal in multiple carriers, cells or bandwidth parts.

[0235] That is, in scheme a, RRC configures the RIV list corresponding to the required bitmap code point, and DCI indicates the frequency domain resources through the index corresponding to the bitmap code point;

[0236] (1) If a separate RRC configuration RIV list is performed for one or more scheduled carriers, cells or BWPs, the size of the FDRA field required for scheduling each carrier, cell or BWP is calculated based on the number of code points in each configured RIV list;

[0237] (2) If a joint RRC configuration RIV list is performed for multiple scheduled carriers, cells or BWPs, the size of the FDRA field required for scheduling the multiple carriers, cells or BWPs is calculated according to the number of code points in the joint configuration RIV list.

[0238] Solution b: an index of a frequency domain resource set, where the frequency domain set meets a preset condition.

[0239] In some implementations of scheme b, the preset conditions include one or more of the following:

[0240] (1) The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value, for example, the first preset value may be predefined or RRC configured;

[0241] (2) The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value, for example, the second preset value may be predefined or RRC configured, such as 50%;

[0242] (3) The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0243] In some implementations of scheme b, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource sets, that is, the number of bits of the frequency domain resource allocation domain required for the carrier, cell or BWP is calculated according to the number of RB sets that meet preset conditions.

[0244] In some implementations of solution b, the index represents the order in which the frequency domain resource sets are arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0245] In an embodiment of the present invention, by reasonably limiting the candidates for frequency domain resource allocation, in a scenario where a DCI schedules multiple carriers, cells or BWPs, it is possible to reduce the control channel resource overhead while maintaining the same scheduling flexibility, thereby improving the demodulation performance of the control channel and the effective coverage of the system.

[0246] The implementation manner of the present invention is described below in conjunction with Embodiment 1, Embodiment 2 and Embodiment 3.

[0247] Embodiment 1:

[0248] When DCI schedules I carriers, cells or BWPs (I>1), the number of RBs of the i-th carrier or BWP is Ni, and the total number of RBs of the scheduled I carriers, cells or BWPs is calculated as ∑Ni. The RBG size of the scheduled i-th carrier, cell or BWP is the same. The RBG size is determined according to Table 2 based on the calculated ∑Ni value and the configuration configured by RRC.

[0249] It should be noted that Table 2 is different from the configuration table for scheduling a single carrier, and a new table may be predefined by protocol, for example, a new BWP size, a new RBG size, or different RB range divisions may be configured in the new table.

[0250] According to the determined RBG size, the RBG corresponding to each bit and the required bit number size are obtained in the i-th carrier, cell or BWP respectively, and are indicated respectively in the DCI.

[0251] Table 2: RBG size

[0252] Carrier Bandwidth Part Size Configuration 1 Configuration 2 1–72 2 4 72–144 4 8 145–275 8 16 276–550 16 16

[0253] Optionally, the RBG size can be explicitly configured via RRC.

[0254] Embodiment 2:

[0255] When DCI schedules I carriers, cells or BWPs (I>1), the number of RBs of the i-th carrier, cell or BWP is Ni. The RBG size is determined according to Ni and the configuration configured by RRC according to Table 2 to obtain RBGi. RBGi is scaled according to a predefined or RRC-configured scaling factor, for example, the scaling factor is K, and a new RBG size RBG'i=K*RBGi of the i-th carrier, cell or BWP is obtained. The RBG corresponding to each bit and the required number of bits are obtained in the i-th carrier, cell or BWP according to RBG'i, and are indicated separately in the DCI.

[0256] Embodiment 3

[0257] RRC configures the table corresponding to the bitmap code point (frequency domain resource allocation bitmap), and DCI indicates the frequency domain resource through the index corresponding to the bitmap code point. For example, for a BWP with 20 RBs and 2 RBG size, 10 bits are required to indicate Type 0 frequency domain resource allocation. RRC configures the corresponding relationship between the bitmap code point and the index, and DCI uses 2 bits to indicate the FDRA value.

[0258] Table 3: Correspondence between bitmap code points and indexes.

[0259] Index Type 0 FDRA 0 1010101010 1 0101010101 2 1101001001 3 1001001011

[0260] Embodiment 4:

[0261] The frequency domain RBs for restricted scheduling need to be greater than half of the total number of BWP RBs. The Type 0 FDRA values ​​that meet this condition are sorted and indicated according to the sorted index. For example, if the number of RBs in a BWP is 10 and the RBG size is 2, the Type 0 FDRA values ​​that meet the condition are 00111, 01101, 01110, 01111, 10011, 10101, 10110, 10111, 11001, 11010, 11011, 11100, 11101, 11110, 11111, etc., a total of 15 possibilities, which need to be indicated with 4 bits. For example, the FDRA value represented by 0000 is 00111.

[0262] See also Figure 6 The embodiment of the present invention further provides a terminal, the terminal 600 includes:

[0263] A first receiving module 601 is used to receive first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0264] The first processing module 602 is used to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts according to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit.

[0265] In some implementations, the terminal 600 further includes:

[0266] A second processing module, configured to determine the frequency domain resource group sizes of the plurality of carriers, cells or bandwidth portions;

[0267] The third processing module is used to obtain the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

[0268] Optionally, the frequency domain resource group sizes of multiple carriers, cells or bandwidth parts are configured on the network side.

[0269] Optionally, the second processing module is further used to: obtain the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity;

[0270] The first quantity includes any one of the following:

[0271] The total number of frequency domain resources of the multiple carriers;

[0272] The total number of frequency domain resources of the multiple cells;

[0273] The total number of frequency domain resources of the plurality of bandwidth parts;

[0274] a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers;

[0275] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells;

[0276] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

[0277] In some implementations, the terminal 600 further includes:

[0278] A fourth processing module, configured to obtain a frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the number of frequency domain resources of each scheduled carrier, cell or bandwidth part;

[0279] A fifth processing module, configured to perform scaling processing on the frequency domain resource group size of each scheduled carrier, cell or bandwidth part;

[0280] The sixth processing module is used to obtain the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the scaled frequency domain resource group size of each scheduled carrier, cell or bandwidth part.

[0281] In some implementations, the fifth processing module is further configured to: scale the frequency domain resource group size of each scheduled carrier, cell, or bandwidth part according to a scaling factor;

[0282] The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

[0283] In some embodiments, the size of the frequency domain resource allocation indication field of the first downlink control information is: ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

[0284] In some implementations, the frequency domain resources of the terminal on the multiple carriers or cells or bandwidth parts include any one of the following:

[0285] frequency domain resources jointly allocated to the terminal on the multiple carriers;

[0286] frequency domain resources jointly allocated to the terminal on the multiple cells;

[0287] jointly allocating frequency domain resources for the terminal over the plurality of bandwidth portions;

[0288] frequency domain resources allocated to the terminal by each carrier in the multiple carriers;

[0289] frequency domain resources allocated to the terminal by each cell in the multiple cells;

[0290] Each bandwidth part in the multiple bandwidth parts is a frequency domain resource allocated to the terminal.

[0291] The terminal provided in the embodiment of the present invention can execute the above Figure 2 The implementation principle and technical effect of the method embodiment shown are similar, and this embodiment will not be repeated here.

[0292] See also Figure 7 The embodiment of the present invention further provides a network device, the network device 700 includes:

[0293] A first sending module 701, configured to send first downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0294] Among them, the first downlink control information is used to indicate the terminal, based on the first downlink control information, the number of bits required for the frequency domain resource allocation of each carrier, cell or bandwidth part scheduled and the frequency domain resource group corresponding to each bit, to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts.

[0295] In some implementations, the network device 700 further includes:

[0296] The determination module is used to determine the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit.

[0297] In some implementations, the network device 700 further includes:

[0298] An eighth processing module, configured to determine a frequency domain resource group size for the plurality of carriers, cells or bandwidth portions;

[0299] The ninth processing module is used to obtain the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

[0300] Optionally, the eighth processing module is further used to: obtain the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity;

[0301] The first quantity includes any one of the following:

[0302] The total number of frequency domain resources of the multiple carriers;

[0303] The total number of frequency domain resources of the multiple cells;

[0304] The total number of frequency domain resources of the plurality of bandwidth parts;

[0305] a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers;

[0306] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells;

[0307] The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

[0308] In some implementations, the network device 700 further includes:

[0309] A tenth processing module, configured to obtain a frequency domain resource group size of each carrier, cell or bandwidth part according to the number of frequency domain resources of each carrier, cell or bandwidth part being scheduled;

[0310] An eleventh processing module is used to scale the frequency domain resource group size of each scheduled carrier, cell or bandwidth part;

[0311] The twelfth processing module is used to obtain the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the scaled frequency domain resource group size of the carrier, cell or bandwidth part.

[0312] In some implementations, the eleventh processing module is further used to: perform scaling processing on the frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the scaling factor;

[0313] The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

[0314] In some embodiments, the size of the frequency domain resource allocation indication field of the first downlink control information is: ∑Ni, Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

[0315] The network device provided by the embodiment of the present invention can execute the above Figure 3 The implementation principle and technical effect of the method embodiment shown are similar, and this embodiment will not be repeated here.

[0316] See also Figure 8 The embodiment of the present invention further provides a terminal, the terminal 800 includes:

[0317] The second receiving module 801 is used to receive second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0318] A thirteenth processing module 802 is configured to obtain frequency domain resources of the terminal on multiple carriers, cells or bandwidth parts according to the frequency domain resource allocation field in the second downlink control information;

[0319] The frequency domain resource allocation domain includes: an index corresponding to a frequency domain resource allocation bitmap, or an index corresponding to a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0320] In some implementations, the terminal 800 further includes:

[0321] The third receiving module is used to receive a list of resource indication values ​​configured by the network device for each scheduled carrier, cell or bandwidth part, wherein the index represents the position of the frequency domain resource allocation bitmap in the resource indication value list, or to receive a list of resource indication values ​​jointly configured by the network device for multiple carriers, cells or bandwidth parts, wherein the index represents the position of the frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0322] In some embodiments, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each carrier, cell or bandwidth part, or the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0323] In some implementations, the frequency domain resource allocation bitmap indicates frequency domain resources allocated to the terminal in one carrier, cell, or bandwidth portion, or indicates frequency domain resources jointly allocated to the terminal in multiple carriers, cells, or bandwidth portions.

[0324] In some implementations, the preset conditions include one or more of the following:

[0325] The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value;

[0326] The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value;

[0327] The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0328] In some implementations, the size of the frequency domain resource allocation field is related to the number of the frequency domain resource sets.

[0329] In some implementations, the index of the frequency domain resource set indicates the order in which the frequency domain resource set is arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0330] The terminal provided in the embodiment of the present invention can execute the above Figure 4 The implementation principle and technical effect of the method embodiment shown are similar, and this embodiment will not be repeated here.

[0331] See also Fig. 9 The embodiment of the present invention further provides a network device, the network device 900 includes:

[0332] A second sending module 901, configured to send second downlink control information for scheduling multiple carriers, cells or bandwidth parts;

[0333] The frequency domain resource allocation field of the second downlink control information includes: an index of a frequency domain resource allocation bitmap, or an index of a frequency domain resource set, and the frequency domain resource set meets a preset condition.

[0334] In some implementations, the network device 900 further includes:

[0335] The third sending module is used to send a list of resource indication values ​​configured for each scheduled carrier, cell or bandwidth part, and the index represents the position of the frequency domain resource allocation bitmap in the resource indication value list, or to send a list of resource indication values ​​jointly configured for multiple carriers, cells or bandwidth parts, and the index represents the position of the frequency domain resource allocation bitmap in the jointly configured resource indication value list.

[0336] In some embodiments, the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the resource indication value list configured for each carrier, cell or bandwidth part, or the size of the frequency domain resource allocation domain is related to the number of frequency domain resource allocation bitmaps in the jointly configured resource indication value list.

[0337] In some implementations, the preset conditions include one or more of the following:

[0338] The number of frequency domain resources in the frequency domain resource set is greater than or equal to a first preset value;

[0339] The ratio of the number of frequency domain resources in the frequency domain resource set to the number of allocatable frequency domain resources of the carrier, cell or bandwidth part is greater than or equal to a second preset value;

[0340] The frequency domain resources in the frequency domain resource set are non-continuous frequency domain resources.

[0341] In some implementations, the size of the frequency domain resource allocation field is related to the number of the frequency domain resource sets.

[0342] In some implementations, the index of the frequency domain resource set indicates the order in which the frequency domain resource set is arranged from small to large or from large to small according to the length of the corresponding bitmap.

[0343] The network device provided by the embodiment of the present invention can execute the above Figure 5 The implementation principle and technical effect of the method embodiment shown are similar, and this embodiment will not be repeated here.

[0344] See also Fig.10 , Fig.10 is a structural diagram of a communication device applied in an embodiment of the present invention, such as Fig.10 As shown, the communication device 1000 includes: a processor 1001, a transceiver 1002, a memory 1003 and a bus interface.

[0345] In one embodiment of the present invention, the communication device 1000 further includes: a computer program stored in the memory 1003 and executable on the processor 1001, the computer program being executed by the processor 1001 to implement Figure 2 , Figure 3 , Figure 4 or Figure 5 Steps in the illustrated embodiment.

[0346] exist Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1001 and memory represented by memory 1003. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1002 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and it is understood that the transceiver 1002 is an optional component.

[0347] The processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1003 can store data used by the processor 1001 when performing operations.

[0348] The communication device provided in the embodiment of the present invention can execute the above Figure 2 , Figure 3 , Figure 4 or Figure 5 The implementation principle and technical effect of the method embodiment shown are similar, and this embodiment will not be repeated here.

[0349] The embodiment of the present invention further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction to implement the above Figure 2 , Figure 3 , Figure 4 or Figure 5 The various processes of the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0350] It should be understood that the chip mentioned in the embodiment of the present invention may also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0351] The steps of the method or algorithm described in conjunction with the disclosure of the present invention may be implemented in hardware or by executing software instructions by a processor. The software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in an application specific integrated circuit (ASIC). In addition, the ASIC may be located in a core network interface device. Of course, the processor and the storage medium may also exist in the core network interface device as discrete components.

[0352] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented using software, the functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that a general or special-purpose computer can access.

[0353] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solution of the present invention should be included in the scope of protection of the present invention.

[0354] Those skilled in the art will appreciate that the embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present invention may take the form of complete hardware embodiments, complete software embodiments, or embodiments combining software and hardware. Moreover, the embodiments of the present invention may take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0355] The embodiments of the present invention are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0356] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0357] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0358] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A frequency domain resource allocation method, applied to a terminal, It is characterized in that include: receiving first downlink control information for simultaneously scheduling a plurality of carriers, cells or bandwidth portions; Obtain, according to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit, the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts; The method further comprises: determining frequency domain resource group sizes for the plurality of carriers, cells or bandwidth portions; According to the frequency domain resource group size, the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit are obtained.

2. The method according to claim 1, It is characterized in that The frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts are configured on the network side.

3. The method according to claim 1, It is characterized in that The determining of the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts comprises: Obtaining the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity; The first quantity includes any one of the following: The total number of frequency domain resources of the multiple carriers; The total number of frequency domain resources of the multiple cells; The total number of frequency domain resources of the plurality of bandwidth parts; a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers; The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells; The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

4. The method according to claim 1, It is characterized in that The method further comprises: Obtaining a frequency domain resource group size for each scheduled carrier, cell or bandwidth part according to the number of frequency domain resources for each scheduled carrier, cell or bandwidth part; Scaling the frequency domain resource group size of each carrier, cell or bandwidth part being scheduled; According to the scaled frequency domain resource group size of each scheduled carrier, cell or bandwidth part, the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit are obtained.

5. The method according to claim 4, It is characterized in that The scaling process of the frequency domain resource group size of each scheduled carrier, cell or bandwidth part includes: Scaling the frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the scaling factor; The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

6. The method according to claim 1, It is characterized in that The size of the frequency domain resource allocation indication field of the first downlink control information is: , Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

7. The method according to claim 1, It is characterized in that The frequency domain resources of the terminal on the multiple carriers or cells or bandwidth parts include any one of the following: frequency domain resources jointly allocated to the terminal on the multiple carriers; frequency domain resources jointly allocated to the terminal on the multiple cells; jointly allocating frequency domain resources for the terminal over the plurality of bandwidth portions; frequency domain resources allocated to the terminal by each carrier in the multiple carriers; frequency domain resources allocated to the terminal by each cell in the multiple cells; Each bandwidth part in the multiple bandwidth parts is a frequency domain resource allocated to the terminal.

8. A frequency domain resource allocation method, applied to network equipment, It is characterized in that include: Sending first downlink control information for simultaneously scheduling multiple carriers, cells or bandwidth parts; The first downlink control information is used to instruct the terminal to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts based on the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part, and the frequency domain resource group corresponding to each bit; The method further comprises: determining frequency domain resource group sizes for the plurality of carriers, cells or bandwidth portions; According to the frequency domain resource group size, the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit are obtained.

9. The method according to claim 8, It is characterized in that The determining of the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts comprises: Obtaining the frequency domain resource group sizes of the multiple carriers, cells or bandwidth parts according to the correspondence between the number of frequency domain resources and the frequency domain resource group size and the first quantity; The first quantity includes any one of the following: The total number of frequency domain resources of the multiple carriers; The total number of frequency domain resources of the multiple cells; The total number of frequency domain resources of the plurality of bandwidth parts; a maximum number of frequency domain resources or a minimum number of frequency domain resources in at least some of the multiple carriers; The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the multiple cells; The maximum number of frequency domain resources or the minimum number of frequency domain resources in at least some of the bandwidth parts among the multiple bandwidth parts.

10. The method according to claim 8, It is characterized in that The method further comprises: Obtaining a frequency domain resource group size for each scheduled carrier, cell or bandwidth part according to the number of frequency domain resources for each scheduled carrier, cell or bandwidth part; Scaling the frequency domain resource group size of each carrier, cell or bandwidth part being scheduled; According to the scaled frequency domain resource group size of the carrier, cell or bandwidth part, the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit are obtained.

11. The method according to claim 10, It is characterized in that The scaling process of the frequency domain resource group size of each scheduled carrier, cell or bandwidth part includes: Scaling the frequency domain resource group size of each scheduled carrier, cell or bandwidth part according to the scaling factor; The scaling factor is agreed upon by the protocol, or the scaling factor is configured on the network side, or the scaling factor is obtained according to the number of carriers, cells or bandwidth parts scheduled by the first downlink control information.

12. The method according to claim 8, It is characterized in that The size of the frequency domain resource allocation indication field of the first downlink control information is: , Ni is the frequency domain resource allocation bitmap size determined based on the frequency domain resource group size of the scheduled i-th carrier, cell or bandwidth part, and i is a natural number.

13. A terminal, It is characterized in that include: A first receiving module, configured to receive first downlink control information for scheduling multiple carriers, cells or bandwidth parts; A first processing module, configured to obtain, according to the first downlink control information, the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and the frequency domain resource group corresponding to each bit, the frequency domain resources allocated to the terminal by the multiple carriers, cells or bandwidth parts; Wherein, the terminal further includes: A second processing module, configured to determine the frequency domain resource group sizes of the plurality of carriers, cells or bandwidth portions; The third processing module is used to obtain the number of bits required for frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

14. A network device, It is characterized in that include: A first sending module, used for sending first downlink control information for scheduling multiple carriers, cells or bandwidth parts; The first downlink control information is used to indicate the number of bits required for the frequency domain resource allocation of each carrier, cell or bandwidth part scheduled and the frequency domain resource group corresponding to each bit to obtain the frequency domain resources of the terminal on the multiple carriers, cells or bandwidth parts based on the first downlink control information; The network device also includes: An eighth processing module, configured to determine a frequency domain resource group size for the plurality of carriers, cells or bandwidth portions; The ninth processing module is used to obtain the number of bits required for the frequency domain resource allocation of each scheduled carrier, cell or bandwidth part and / or the frequency domain resource group corresponding to each bit according to the size of the frequency domain resource group.

15. A communication device, It is characterized in that include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the frequency domain resource allocation method according to any one of claims 1 to 12 are implemented.

16. A readable storage medium, It is characterized in that The readable storage medium stores a program, and when the program is executed by a processor, the steps of the frequency domain resource allocation method according to any one of claims 1 to 12 are implemented.