Frequency domain resource configuration method and apparatus

Abstract

The embodiment of the application discloses a frequency domain resource configuration method and device. The method comprises the following steps: receiving indication information sent by a network device; determining frequency domain resources occupied by a control resource set (CORESET) according to the indication information, wherein the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or the frequency domain resources occupied by the CORESET are at least two groups of discontinuous frequency domain resource units, the group of frequency domain resource units is obtained by dividing a plurality of frequency domain resource units according to one of at least two granularities, the allocation mode of the frequency domain resources of a terminal device can be changed or the allocation granularity of the frequency domain resources can be flexibly configured, so that the terminal device can support a higher aggregation level as much as possible, the transmission performance of a downlink channel is effectively improved, the coverage of the downlink channel is enhanced, the system communication efficiency is improved, resource waste is effectively reduced, and the resource utilization rate is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a frequency domain resource configuration method and apparatus. Background Technology

[0002] In related technologies, the terminal device control resource set (CORESET) occupies 1 to 3 consecutive symbols in the time domain, and in the frequency domain, it is configured with frequency domain resources in a manner similar to the Physical Downlink Shared Channel (PDSCH) resource allocation type 0.

[0003] Release 18 proposes further bandwidth reduction for RedCap terminal devices to support low-data-rate and cost-sensitive services such as factory sensors. However, it may still support subcarrier spacing configurations such as 15kHz and 30kHz, resulting in a reduction of available frequency domain resources within the bandwidth. If the CORESET frequency domain resource allocation method from related technologies is still used, some frequency domain resources within the bandwidth may remain unused. Summary of the Invention

[0004] A first aspect of this application provides a frequency domain resource allocation method, which is executed by a terminal device and includes:

[0005] Receive instruction information sent by network devices;

[0006] Based on the indicated information, determine the frequency domain resources occupied by the control resource set CORESET;

[0007] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0008] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0009] Optionally, determining the frequency domain resources occupied by the control resource set CORESET based on the indication information includes:

[0010] Based on the indicated information, determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

[0011] Optionally, determining the frequency domain resources occupied by the control resource set CORESET based on the indication information includes:

[0012] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0013] Based on the indicated information, determine the size of the frequency domain resources occupied by the CORESET;

[0014] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0015] Optionally, determining the frequency domain resources occupied by the control resource set CORESET based on the indication information includes:

[0016] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0017] The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device;

[0018] The size of the frequency domain resources occupied by the CORESET is determined based on the highest aggregation level of the terminal device and the number of time domain symbols; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time domain symbols.

[0019] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0020] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0021] Optionally, the method further includes:

[0022] In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0023] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0024] Optionally, the granularity is determined based on at least one of the following:

[0025] Particle size indication information;

[0026] The bandwidth supported by the terminal device;

[0027] The number of bits in the indication information;

[0028] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0029] The number of time-domain symbols configured in the network device.

[0030] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0031] A second aspect of this application provides a frequency domain resource allocation method, which is executed by a network device and includes:

[0032] Send instruction information to the terminal device;

[0033] The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET;

[0034] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0035] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0036] Optionally, the indication information is used to determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET;

[0037] The starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources are used to determine the frequency domain resources occupied by the CORESET.

[0038] Optionally, the indication information is used to determine the size of the frequency domain resources occupied by the CORESET;

[0039] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0040] Optionally, the indication information is used to indicate the highest aggregation level of the terminal device and the number of time-domain symbols;

[0041] The highest aggregation level and the number of time-domain symbols of the terminal device are used to determine the size of the frequency domain resources occupied by the CORESET; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time-domain symbols.

[0042] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0043] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0044] Optionally, in response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0045] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0046] Optionally, the granularity is determined based on at least one of the following:

[0047] Particle size indication information;

[0048] The bandwidth supported by the terminal device;

[0049] The number of bits in the indication information;

[0050] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0051] The number of time-domain symbols configured in the network device.

[0052] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0053] A third aspect of this application provides a frequency domain resource allocation apparatus, which is applied to a terminal device and includes:

[0054] The transceiver unit is used to receive instruction information sent by network devices;

[0055] The processing unit is configured to determine the frequency domain resources occupied by the control resource set CORESET based on the indication information.

[0056] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0057] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0058] Optionally, the processing unit is specifically used for:

[0059] Based on the indicated information, determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

[0060] Optionally, the processing unit is specifically used for:

[0061] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0062] Based on the indicated information, determine the size of the frequency domain resources occupied by the CORESET;

[0063] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0064] Optionally, the processing unit is specifically used for:

[0065] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0066] The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device;

[0067] The size of the frequency domain resources occupied by the CORESET is determined based on the highest aggregation level of the terminal device and the number of time domain symbols; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time domain symbols.

[0068] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0069] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0070] Optionally, the processing unit is further configured to:

[0071] In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0072] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0073] Optionally, the granularity is determined based on at least one of the following:

[0074] Particle size indication information;

[0075] The bandwidth supported by the terminal device;

[0076] The number of bits in the indication information;

[0077] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0078] The number of time-domain symbols configured in the network device.

[0079] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0080] A fourth aspect of this application provides a frequency domain resource configuration apparatus, which is applied to a network device, and the apparatus includes:

[0081] The transceiver unit is used to send instruction information to the terminal device;

[0082] The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET;

[0083] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0084] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0085] Optionally, the indication information is used to determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET;

[0086] The starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources are used to determine the frequency domain resources occupied by the CORESET.

[0087] Optionally, the indication information is used to determine the size of the frequency domain resources occupied by the CORESET;

[0088] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0089] Optionally, the indication information is used to indicate the highest aggregation level of the terminal device and the number of time-domain symbols;

[0090] The highest aggregation level and the number of time-domain symbols of the terminal device are used to determine the size of the frequency domain resources occupied by the CORESET; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time-domain symbols.

[0091] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0092] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0093] Optionally, in response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0094] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0095] Optionally, the granularity is determined based on at least one of the following:

[0096] Particle size indication information;

[0097] The bandwidth supported by the terminal device;

[0098] The number of bits in the indication information;

[0099] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0100] The number of time-domain symbols configured in the network device.

[0101] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0102] A fifth aspect of this application provides a communication device, the device including a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the frequency domain resource allocation method described in the first aspect of the application.

[0103] A sixth aspect of this application provides a communication device, the device including a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the frequency domain resource allocation method described in the second aspect of the application above.

[0104] A seventh aspect of this application provides a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor. The processor is used to execute the code instructions to cause the device to perform the frequency domain resource configuration method described in the first aspect of the application.

[0105] An eighth aspect of this application provides a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, which is used to execute the code instructions to cause the device to perform the frequency domain resource configuration method described in the second aspect of the application.

[0106] A ninth aspect of this application provides a computer-readable storage medium for storing instructions that, when executed, enable the frequency domain resource allocation method described in the first aspect of this application to be implemented.

[0107] A tenth aspect of this application provides a computer-readable storage medium for storing instructions that, when executed, enable the frequency domain resource allocation method described in the second aspect of the application to be implemented.

[0108] The eleventh aspect of this application provides a computer program that, when run on a computer, causes the computer to execute the frequency domain resource allocation method described in the first aspect embodiment.

[0109] The twelfth aspect of this application provides a computer program that, when run on a computer, causes the computer to perform the frequency domain resource allocation method described in the second aspect embodiment.

[0110] This application provides a frequency domain resource configuration method and apparatus. By receiving indication information sent by a network device, the method determines the frequency domain resources occupied by a control resource set (CORESET) based on the indication information. The frequency domain resources occupied by the CORESET are either continuous frequency domain resource units or non-contiguous frequency domain resource units (groups of at least two frequency domain resource units). These grouped frequency domain resource units are obtained by dividing multiple frequency domain resource units according to at least two granularities. This allows the terminal device to support higher aggregation levels by changing the allocation method of frequency domain resources or flexibly configuring the allocation granularity of frequency domain resources. This effectively improves downlink channel transmission performance, enhances downlink channel coverage, increases system communication efficiency, effectively reduces resource waste, and improves resource utilization.

[0111] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0112] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0113] Figure 1a This application provides a schematic diagram of the architecture of a communication system.

[0114] Figure 1b This application provides a schematic diagram of frequency domain resource configuration in a related art.

[0115] Figure 2 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application;

[0116] Figure 3 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application;

[0117] Figure 4 A flowchart illustrating a frequency domain resource allocation method provided in an embodiment of this application;

[0118] Figure 5 A flowchart illustrating a frequency domain resource allocation method provided in an embodiment of this application;

[0119] Figure 6 A flowchart illustrating a frequency domain resource allocation method provided in an embodiment of this application;

[0120] Figure 7 A flowchart illustrating a frequency domain resource allocation method provided in an embodiment of this application;

[0121] Figure 8 This is a schematic diagram of the structure of a frequency domain resource configuration device provided in an embodiment of this application;

[0122] Figure 9 This is a schematic diagram of the structure of a frequency domain resource configuration device provided in an embodiment of this application;

[0123] Figure 10 A schematic diagram of another frequency domain resource configuration device provided in an embodiment of this application;

[0124] Figure 11 This is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure. Detailed Implementation

[0125] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0126] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the embodiments of this application. The singular forms “a” and “the” as used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0127] It should be understood that although the terms first, second, third, etc., may be used to describe various information in the embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words "if" and "suppose" as used herein can be interpreted as "when," "when," or "in response to a determination."

[0128] Embodiments of this application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0129] To better understand the frequency domain resource configuration method disclosed in the embodiments of this application, the communication system to which the embodiments of this application are applicable is described below.

[0130] Please see Figure 1a , Figure 1a This application provides a schematic diagram of the architecture of a communication system. The communication system may include, but is not limited to, a first network device, a second network device, and a terminal device. Figure 1a The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. In actual applications, it may include two or more network devices and two or more terminal devices. Figure 1a The communication system shown is exemplified by a network device 101 and a terminal device 102.

[0131] It should be noted that the technical solutions of this application embodiment can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, fifth-generation mobile communication systems, 5G New Radio systems, or other future new mobile communication systems.

[0132] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a Transmission Reception Point (TRP), a Next Generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a Wireless Fidelity (WiFi) system. This embodiment does not limit the specific technology or device form used in the network device. The network device provided in this embodiment can be composed of a Central Unit (CU) and a Distributed Unit (DU). The CU can also be called a Control Unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0133] The terminal device 102 in this embodiment is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or a RedCap UE, an evolved RedCap UE, etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and so on. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0134] In related technologies, the terminal device's control resource set (CORESET) occupies 1 to 3 consecutive symbols in the time domain, and its frequency domain resources are configured in a manner similar to PDSCH (Physical Downlink Shared Channel) resource allocation type 0. The basic granularity of frequency domain resource allocation is 6 RBs (Resource Blocks).

[0135] Release 18 proposes further reducing the bandwidth of Reduced Capability (RedCap) terminal devices to support low-data-rate and cost-sensitive service types such as factory sensors. At the same time, it may still support subcarrier spacing configurations such as 15KHz and 30KHz, resulting in a reduction of available frequency domain resources within the bandwidth range.

[0136] With a sub-carrier spacing (SCS) of 30 kHz, only 11 radio blocks (RBs) are available within a 5 MHz bandwidth. If the CORESET frequency domain resource configuration method from related technologies is still adopted, configuring CORESET frequency domain resources with a basic granularity of 6 RBs, then for the Physical Downlink Control Channel (PDCCH), some frequency domain resources within the bandwidth may never be utilized, such as... Figure 1b As shown, Figure 1b This is a schematic diagram of frequency domain resource configuration in a related art provided in an embodiment of this application. This reduces the number of REGs included in the CORESET, resulting in the inability to support higher aggregation levels, such as... Figure 1b The highest supported aggregation level (AL) is 2, which affects the coverage and transmission performance of the downlink transmission PDCCH of the terminal device.

[0137] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0138] The frequency domain resource allocation method and apparatus provided in this application will be described in detail below with reference to the accompanying drawings.

[0139] Please see Figure 2 , Figure 2 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a terminal device. Figure 2 As shown, the method may include the following steps:

[0140] Step 201: Receive instruction information sent by the network device.

[0141] In this embodiment of the application, the terminal device receives indication information sent by the network device, which is used to instruct the terminal device to determine the frequency domain resources occupied by the control resource set CORESET.

[0142] In some implementations, the indication information is used to indicate that the frequency domain resources occupied by the CORESET are consecutive frequency domain resource units.

[0143] In some implementations, the indication information includes at least 1 bit, each bit of which can indicate whether the corresponding set of frequency domain resource units is a frequency domain resource occupied by the CORESET.

[0144] Frequency domain resource units can be resource blocks (RBs), physical resource blocks (PRBs), virtual resource blocks (VRBs), common resource blocks (CRBs), etc.

[0145] Step 202: Based on the instruction information, determine the frequency domain resources occupied by the control resource set CORESET, wherein the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0146] In this embodiment of the application, the terminal device can determine the frequency domain resources occupied by CORESET based on the indication information.

[0147] As one implementation of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units.

[0148] In some implementations, the terminal device can determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET based on the indication information, thereby determining the frequency domain resources occupied by the CORESET.

[0149] In some implementations, the terminal device can obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol, and determine the size of the frequency domain resources occupied by the CORESET based on the indication information, thereby determining the frequency domain resources occupied by the CORESET.

[0150] In some implementations, the terminal device can obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol, and determine the highest aggregation level and the number of time domain symbols of the terminal device according to the indication information. Furthermore, based on the highest aggregation level and the number of time domain symbols of the terminal device, the size of the frequency domain resources occupied by the CORESET is determined, thereby determining the frequency domain resources occupied by the CORESET.

[0151] In some implementations, the size of the frequency domain resources occupied by the CORESET can also be determined based on the highest aggregation level of the terminal device, the number of PDCCH candidate channels supported by the highest aggregation level, and the number of time domain symbols.

[0152] Optionally, the size of the frequency domain resource can be matched with the bandwidth supported by the terminal device to avoid resource waste. In this embodiment, matching means that the size of the frequency domain resource is as close as possible to the length of the bandwidth supported by the terminal device.

[0153] It is understood that in the embodiments of this application, the bandwidth supported by the terminal device can be either the full bandwidth or the bandwidth part (BWP).

[0154] In the embodiments of this application, the size of the frequency domain resource can also be referred to as the length of the frequency domain resource, which is the number of frequency domain resource units included in the frequency domain resource.

[0155] As another implementation of this application, the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to one of at least two granularities.

[0156] In some implementations, the indication information includes at least 1 bit, which indicates the position of the at least one group of frequency domain resource units in a plurality of frequency domain resource units configured in the network device, and each bit of the indication information indicates whether the corresponding group of frequency domain resource units is a frequency domain resource occupied by the CORESET.

[0157] In some implementations, the granularity is determined based on at least one of the following: granularity indication information; bandwidth supported by the terminal device; number of bits of the indication information; number of resource element groups (REGs) occupied by the control channel element (CCE); and number of time-domain symbols configured by the network device. This allocation granularity can be flexibly configured according to actual conditions to further improve resource utilization and avoid resource waste.

[0158] In some implementations, releasing the remaining REGs in response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE) can further improve resource utilization and avoid resource waste.

[0159] As mentioned above, in related technologies, the indication information indicates that the frequency domain resources occupied by the CORESET are at least two non-contiguous groups of frequency domain resource units, the group of frequency domain resource units includes 6 frequency domain resource units, and the allocation granularity of the frequency domain resources of the CORESET is 6.

[0160] In some embodiments of this application, the at least two discontinuous frequency domain resource units occupied by the CORESET are obtained by dividing multiple frequency domain resource units according to one of at least two granularities, that is, changing the granularity of frequency domain resource allocation.

[0161] In some embodiments of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units, which means that the frequency domain resource allocation method has been changed.

[0162] In summary, by receiving indication information sent by network devices, the frequency domain resources occupied by the control resource set CORESET are determined based on this indication information. The frequency domain resources occupied by the CORESET are either contiguous frequency domain resource units or a group of at least two non-contiguous frequency domain resource units. This group of frequency domain resource units is obtained by dividing multiple frequency domain resource units according to at least two granularities. By changing the allocation method of frequency domain resources in the terminal device or flexibly configuring the allocation granularity of frequency domain resources, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0163] Please see Figure 3 , Figure 3 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a terminal device. Figure 3 As shown, the method may include the following steps:

[0164] Step 301: Receive instruction information sent by the network device.

[0165] In this embodiment of the application, the terminal device receives indication information sent by the network device, which is used to instruct the terminal device to determine the frequency domain resources occupied by the control resource set CORESET.

[0166] In this embodiment of the application, the indication information can be RIV joint encoding, and the terminal device can determine the starting position and frequency domain resource length allocated to the CORESET based on the RIV encoding.

[0167] RIV encoding is determined by the network device based on the starting position and length of the frequency domain resources allocated to the CORESET. After receiving the RIV encoding, the terminal device can decode it to determine the starting position and length of the frequency domain resources allocated to the CORESET.

[0168] As an example, RIV encoding can be determined in the following way.

[0169] If (L-1)≤|N / 2|, then RIV=N(L-1)+RB START Otherwise, RIV = N(N-L+1) + (N-1-RB) START Where N represents the number of frequency domain resource units included in the bandwidth supported by the terminal device, L represents the size of the frequency domain resource, and RB START It indicates the starting position of the frequency domain resource, and RIV indicates the RIV code, which is a value represented by at least 1 bit.

[0170] Step 302: Based on the instruction information, determine the starting position of the frequency domain resources occupied by the control resource set CORESET and the size of the frequency domain resources occupied by the CORESET.

[0171] In this embodiment of the application, the terminal device can receive the RIV code sent by the network device, and can determine the starting position of the frequency domain resources occupied by the control resource set CORESET and the size of the frequency domain resources occupied by the CORESET based on the RIV code.

[0172] In some implementations, the terminal device can determine the start position and length of the frequency domain resource corresponding to the RIV value by looking up a table based on the RIV code value.

[0173] In some implementations, the terminal device can also decode the RIV code by calculation to determine the starting position and length of the frequency domain resource corresponding to the RIV value.

[0174] As an example, RIVs can be decoded in the following way.

[0175] Assuming P represents the size of the frequency domain resource, O represents the starting position of the frequency domain resource, N represents the number of frequency domain resource units included in the bandwidth of the terminal device, and x represents the RIV value, then we denote:

[0176] a = floor(x / N) + 1, b = x mod N. Here, floor(·) represents rounding down, and mod represents taking the remainder.

[0177] Therefore, it exists:

[0178] If a + b > N, then P = N + 2 - a, O = N - 1 - b. Otherwise, P = a, O = b.

[0179] In this embodiment of the application, after the terminal device determines the starting position and length of the frequency domain resources occupied by the CORESET, it determines the frequency domain resources occupied by the CORESET.

[0180] It is understood that, in the embodiments of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units.

[0181] Furthermore, in some embodiments, in response to the existence of remaining resource groups (REGs) not mapped to a control channel unit (CCE), the remaining REGs are released. This allows REGs that cannot be mapped to a CCE to be released to other terminal devices or channels, thereby further improving resource utilization and reducing resource waste.

[0182] In some implementations, in order to further conserve resources and reduce the waste of frequency domain resources, when configuring the size of the frequency domain resources, the network device determines that the product of the size of the frequency domain resources and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, that is, the number of REGs included in the CORESET is an integer multiple of 6.

[0183] It should be noted that because PDCCH transmission occurs on at least one CCE, and one CCE includes 6 REGs, if the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is not an integer multiple of 6, there may be surplus REGs that cannot be mapped to a CCE. These surplus REGs will never be used for PDCCH transmission, resulting in a waste of frequency domain resources. If the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, then all REGs included in the CORESET can be mapped to a CCE.

[0184] In some implementations, the size of the frequency domain resource may also be determined by considering the aggregation level. When the aggregation level is high, the size of the frequency domain resource matches the bandwidth supported by the terminal device, and the size of the frequency domain resource is as close as possible to the length of the bandwidth supported by the terminal device.

[0185] In summary, by receiving indication information sent by network devices and determining the starting position and size of the frequency domain resources occupied by the control resource set CORESET based on this indication information, the terminal devices can support higher aggregation levels as much as possible by changing the allocation method of frequency domain resources. This effectively improves the transmission performance of the downlink channel, enhances the coverage of the downlink channel, improves system communication efficiency, effectively reduces resource waste, and improves resource utilization.

[0186] Please see Figure 4 , Figure 4 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a terminal device. Figure 4 As shown, the method may include the following steps:

[0187] Step 401: Receive instruction information sent by the network device.

[0188] In this embodiment of the application, the terminal device receives indication information sent by the network device, which is used to instruct the terminal device to determine the frequency domain resources occupied by the control resource set CORESET.

[0189] In this embodiment of the application, the indication information is used to indicate the size of the frequency domain resource.

[0190] Step 402: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol.

[0191] In this embodiment of the application, it is possible to obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol.

[0192] Optionally, the starting position of the frequency domain resource can be the frequency domain resource unit with the lowest frequency of the terminal device's bandwidth, the frequency domain resource unit with the highest frequency of the terminal device's bandwidth, or the center frequency position of the terminal device's bandwidth.

[0193] Step 403: Determine the size of the frequency domain resources occupied by the CORESET based on the instruction information.

[0194] In this embodiment of the application, the indication information is used to indicate the size of the frequency domain resources occupied by the CORESET, and the terminal device can determine the size of the frequency domain resources based on the indication information.

[0195] Step 404: Determine the frequency domain resources occupied by the CORESET based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0196] In this embodiment of the application, after the terminal device determines the starting position and length of the frequency domain resources occupied by the CORESET, it can determine the frequency domain resources occupied by the CORESET based on the starting position and length of the frequency domain resources.

[0197] It is understood that, in the embodiments of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units.

[0198] Optionally, the frequency domain resources occupied by the CORESET can be determined as the first N frequency domain resource units in the bandwidth of the terminal device, from low to high, based on the starting position of the acquired frequency domain resource being the lowest frequency frequency resource unit in the bandwidth of the terminal device, and the size N of the frequency domain resource indicated by the indication information.

[0199] Optionally, the frequency domain resources occupied by the CORESET can be determined as the first N frequency domain resource units in the bandwidth of the terminal device, from high to low, based on the starting position of the frequency domain resource obtained as the highest frequency of the bandwidth of the terminal device, and the size N of the frequency domain resource indicated by the indication information.

[0200] Optionally, based on the starting position of the acquired frequency domain resource as the center frequency position of the terminal device's bandwidth, and the size N of the frequency domain resource indicated by the indication information, the frequency domain resource occupied by the CORESET can be determined as follows: floor(N / 2) frequency domain resource units are allocated upwards (towards higher frequencies) from the center frequency, and N-floor(N / 2) frequency domain resource units are allocated downwards (towards lower frequencies) from the center frequency. Alternatively, the frequency domain resource occupied by the CORESET can be determined as follows: floor(N / 2) frequency domain resource units are allocated downwards (towards lower frequencies) from the center frequency, and N-floor(N / 2) frequency domain resource units are allocated upwards (towards higher frequencies) from the center frequency. Here, floor(·) represents rounding down.

[0201] Furthermore, in some embodiments, in response to the existence of remaining resource groups (REGs) not mapped to a control channel unit (CCE), the remaining REGs are released. This allows REGs that cannot be mapped to a CCE to be released to other terminal devices or channels, thereby further improving resource utilization and reducing resource waste.

[0202] In some implementations, in order to further conserve resources and reduce the waste of frequency domain resources, when configuring the size of the frequency domain resources, the network device determines that the product of the size of the frequency domain resources and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, that is, the number of REGs included in the CORESET is an integer multiple of 6.

[0203] It should be noted that because PDCCH transmission occurs on at least one CCE, and one CCE includes 6 REGs, if the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is not an integer multiple of 6, there may be surplus REGs that cannot be mapped to a CCE. These surplus REGs will never be used for PDCCH transmission, resulting in a waste of frequency domain resources. If the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, then all REGs included in the CORESET can be mapped to a CCE.

[0204] In some implementations, the size of the frequency domain resource may also be determined by considering the aggregation level. When the aggregation level is high, the size of the frequency domain resource matches the bandwidth supported by the terminal device, and the size of the frequency domain resource is as close as possible to the length of the bandwidth supported by the terminal device.

[0205] In summary, by receiving indication information sent by network devices, the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol is obtained. Based on this indication information, the size of the frequency domain resources occupied by the CORESET is determined. Based on the starting position and the size of the frequency domain resources occupied by the CORESET, the frequency domain resources occupied by the CORESET are determined. By changing the allocation method of frequency domain resources of terminal devices, the terminal devices can support higher aggregation levels as much as possible, effectively improve the transmission performance of downlink channels, enhance downlink channel coverage, improve system communication efficiency, effectively reduce resource waste, and improve resource utilization.

[0206] Please see Figure 5 , Figure 5 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a terminal device. Figure 5 As shown, the method may include the following steps:

[0207] Step 501: Receive instruction information sent by the network device.

[0208] In this embodiment of the application, the terminal device receives indication information sent by the network device, which is used to instruct the terminal device to determine the frequency domain resources occupied by the control resource set CORESET.

[0209] In this embodiment of the application, the indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device.

[0210] Step 502: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol.

[0211] In this embodiment of the application, it is possible to obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol.

[0212] Optionally, the starting position of the frequency domain resource can be the frequency domain resource unit with the lowest frequency of the terminal device's bandwidth, the frequency domain resource unit with the highest frequency of the terminal device's bandwidth, or the center frequency position of the terminal device's bandwidth.

[0213] Step 503: Determine the size of the frequency domain resources occupied by the CORESET based on the highest aggregation level of the terminal device indicated by the instruction information and the number of time domain symbols.

[0214] The size of the frequency domain resource is functionally related to the highest aggregation level of the terminal device and the number of time domain symbols.

[0215] In this embodiment of the application, the size of the frequency domain resource can be determined according to certain rules based on the highest aggregation level of the terminal device and the number of time domain symbols.

[0216] As an example, if the size of the frequency domain resource is N, the highest aggregation level AL of the terminal device is a, and the number of time domain symbols is s, the rule can be N ≥ a × 6 / s. For instance, if the highest aggregation level of the terminal device is 4 and the number of time domain symbols is 3, then the size of the frequency domain resource is at least 8 frequency domain resource units.

[0217] In some implementations, the size of the frequency domain resources occupied by the CORESET can also be determined according to certain rules based on the highest aggregation level of the terminal device, the number of PDCCH candidate channels supported by the highest aggregation level, and the number of time domain symbols.

[0218] As an example, if the size of the frequency domain resource is N, the highest aggregation level AL of the terminal device is a, the number of PDCCH candidate channels supported by the highest aggregation level is M, and the number of time domain symbols is s, the rule can be N ≥ a × 6 × M / s. For instance, if the highest aggregation level of the terminal device is 4, the number of PDCCH candidate channels supported by the highest aggregation level is 2, and the number of time domain symbols is 3, then the size of the frequency domain resource is at least 16 frequency domain resource units.

[0219] Step 504: Determine the frequency domain resources occupied by the CORESET based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0220] In this embodiment of the application, after the terminal device determines the starting position and length of the frequency domain resources occupied by the CORESET, it can determine the frequency domain resources occupied by the CORESET based on the starting position and length of the frequency domain resources.

[0221] It is understood that, in the embodiments of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units.

[0222] Optionally, the frequency domain resources occupied by the CORESET can be determined as the first N frequency domain resource units in the bandwidth of the terminal device, from low to high, based on the starting position of the frequency domain resource obtained as the lowest frequency frequency resource unit of the terminal device bandwidth and the size N of the frequency domain resource determined in step 503.

[0223] Optionally, the frequency domain resources occupied by the CORESET can be determined as the first N frequency domain resource units in the bandwidth of the terminal device, from high to low, based on the starting position of the frequency domain resource obtained as the highest frequency of the terminal device bandwidth and the size N of the frequency domain resource determined in step 503.

[0224] Optionally, based on the starting position of the acquired frequency domain resource as the center frequency position of the terminal device's bandwidth, and the size N of the frequency domain resource determined in step 503, the frequency domain resource occupied by the CORESET can be determined as follows: floor(N / 2) frequency domain resource units are allocated upwards (towards higher frequencies) from the center frequency, and N-floor(N / 2) frequency domain resource units are allocated downwards (towards lower frequencies) from the center frequency. Alternatively, the frequency domain resource occupied by the CORESET can be determined as follows: floor(N / 2) frequency domain resource units are allocated downwards (towards lower frequencies) from the center frequency, and N-floor(N / 2) frequency domain resource units are allocated upwards (towards higher frequencies) from the center frequency. Here, floor(·) represents rounding down.

[0225] Furthermore, in some embodiments, in response to the existence of remaining resource groups (REGs) not mapped to a control channel unit (CCE), the remaining REGs are released. This allows REGs that cannot be mapped to a CCE to be released to other terminal devices or channels, thereby further improving resource utilization and reducing resource waste.

[0226] In some implementations, in order to further conserve resources and reduce the waste of frequency domain resources, when configuring the size of the frequency domain resources, the network device determines that the product of the size of the frequency domain resources and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, that is, the number of REGs included in the CORESET is an integer multiple of 6.

[0227] It should be noted that because PDCCH transmission occurs on at least one CCE, and one CCE includes 6 REGs, if the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is not an integer multiple of 6, there may be surplus REGs that cannot be mapped to a CCE. These surplus REGs will never be used for PDCCH transmission, resulting in a waste of frequency domain resources. If the product of the size of the frequency domain resource and the number of symbols occupied in the time domain of the CORESET configured by the network device is divisible by 6, then all REGs included in the CORESET can be mapped to a CCE.

[0228] In some implementations, the size of the frequency domain resource may also be determined by considering the aggregation level. When the aggregation level is high, the size of the frequency domain resource matches the bandwidth supported by the terminal device, and the size of the frequency domain resource is as close as possible to the bandwidth supported by the terminal device.

[0229] In summary, by receiving indication information sent by network devices, the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol is obtained. Based on the highest aggregation level of the terminal device indicated by the indication information and the number of time domain symbols, the size of the frequency domain resources occupied by the CORESET is determined. Based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources, the frequency domain resources occupied by the CORESET are determined. By changing the allocation method of frequency domain resources of the terminal device, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0230] Please see Figure 6 , Figure 6 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a terminal device. Figure 5 As shown, the method may include the following steps:

[0231] Step 601: Receive instruction information sent by the network device.

[0232] In this embodiment of the application, the terminal device receives indication information sent by the network device, which is used to instruct the terminal device to determine the frequency domain resources occupied by the control resource set CORESET.

[0233] In this embodiment of the application, the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups. The indication information is used to indicate the position of at least one frequency domain resource unit group in the multiple frequency domain resource units configured in the network device. The indication information includes at least 1 bit, and each bit of the indication information can indicate whether the corresponding group of frequency domain resource units is the frequency domain resource occupied by the CORESET.

[0234] Frequency domain resource units can be resource blocks (RB), physical resource blocks (PRB), virtual resource blocks (VRB), common resource blocks (CRB), etc.

[0235] Step 602: Based on the instruction information, determine the frequency domain resources occupied by the control resource set CORESET, wherein the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, and the frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0236] In this embodiment of the application, based on the indication information, it is possible to determine at least two non-contiguous frequency domain resource unit groups occupied by the CORESET. These frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least two granularities.

[0237] It can be understood that this granularity is the number of frequency domain resource units included in a frequency domain resource group, and also the number of frequency domain resource units corresponding to each bit in the indication information.

[0238] As an example, the granularity can optionally be 2, 3, or 6. That is, a frequency domain resource group of this CORESET can include 2 frequency domain resource units, 3 frequency domain resource units, or 6 frequency domain resource units. In other words, 1 bit in the indication information can indicate the corresponding 2 frequency domain resource units, 3 frequency domain resource units, or 6 frequency domain resource units.

[0239] It should be noted that, in the embodiments of this application, in at least one frequency domain resource group of a CORESET, the number of frequency domain resource units included in each frequency domain resource group is the same.

[0240] In this embodiment, the granularity of frequency domain resource allocation is changed, which enables the terminal device to support higher aggregation levels by flexibly configuring the allocation granularity of frequency domain resources.

[0241] In some implementations, this granularity can be determined based on at least one of the following:

[0242] Particle size indication information;

[0243] The bandwidth supported by the terminal device;

[0244] The number of bits indicating the information;

[0245] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0246] The number of time-domain symbols configured in the network device.

[0247] Optionally, the allocation granularity of the frequency domain resources of the CORESET can be determined from a granularity set including at least two granularities based on granularity indication information. For example, if the granularity set is {2,3,6}, the terminal device can determine the allocation granularity of the frequency domain resources of the CORESET from the set {2,3,6} based on the granularity indication information.

[0248] Optionally, the granularity of frequency domain resource allocation for the CORESET can be determined based on the bandwidth supported by the terminal device and the number of bits in the indication information. Based on the bandwidth supported by the terminal device and the number of bits in the indication information, the number of frequency domain resource units indicated by each bit of the indication information can be determined, thus determining the granularity of frequency domain resource allocation for the CORESET.

[0249] It is understood that in the embodiments of this application, the bandwidth supported by the terminal device can be either full bandwidth or partial bandwidth (BWP).

[0250] Optionally, the granularity of frequency domain resource allocation for the CORESET can be determined based on the number of REGs occupied by the CCE and the number of time-domain symbols configured in the network device.

[0251] Optionally, the granularity of frequency domain resource allocation for the CORESET can be determined based on the number of time-domain symbols configured in the network device. As an example, for instance, the granularity of frequency domain resource allocation for the CORESET can be determined to be 3 based on the number of time-domain symbols configured in the network device being 2 or 4; or the granularity of frequency domain resource allocation for the CORESET can be determined to be 2 based on the number of time-domain symbols configured in the network device being 3.

[0252] In some implementations, there is at least one combination of time-domain symbol count and granularity, which can be indicated by an index that corresponds to the number of time-domain symbols and the corresponding granularity.

[0253] Furthermore, in some embodiments, in response to the existence of remaining resource groups (REGs) not mapped to a control channel unit (CCE), the remaining REGs are released. This allows REGs that cannot be mapped to a CCE to be released to other terminal devices or channels, thereby further improving resource utilization and reducing resource waste.

[0254] In some implementations, when the aggregation level is high, the frequency domain resources of the CORESET are matched with the bandwidth supported by the terminal device, and the size of the frequency domain resources is as close as possible to the bandwidth supported by the terminal device.

[0255] In summary, by receiving indication information sent by network devices, the frequency domain resources occupied by the control resource set CORESET are determined based on this indication information. The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups. These frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least two granularities. By flexibly configuring the allocation granularity of frequency domain resources, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0256] It should be noted that, because the resource configuration method of CORESET#0 is different from other CORESETs, in the embodiments of this application, if the control resource set CORESET is CORESET#0, the indication information is the Remaining Minimum System Information (RMSI). The RMSI signaling is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0257] As an example, when the subcarrier spacing (SCS) is 30 kHz, the combination of at least one frequency domain resource length and the corresponding number of symbols agreed upon in the protocol can be shown in the table below.

[0258]

[0259] Table 1 shows the frequency domain resource length and corresponding symbol count configuration for CORESET#0.

[0260] To improve resource utilization, reduce unnecessary resource waste, and enhance transmission efficiency and quality, when designing the combination of frequency domain resource length and corresponding symbol number for CORESET#0, we can try to ensure that the frequency domain resource length does not exceed the bandwidth supported by the terminal device, and that the number of REGs (i.e., the product of the number of RBs and the number of symbols) included in the combination of frequency domain resource length and corresponding symbol number is as much as possible a multiple of 6, etc.

[0261] It is understood that this table is only an example, exemplarily providing some possible combinations of frequency domain resource lengths and corresponding symbol counts for CORESET#0. More combinations can be designed to meet and adapt to more scenarios and bandwidth requirements. This table is only an example and does not limit the embodiments of this application.

[0262] Please see Figure 7 , Figure 7 This is a flowchart illustrating a frequency domain resource configuration method provided in an embodiment of this application. It should be noted that the frequency domain resource configuration method in this embodiment is executed by a network device. Figure 7 As shown, the method may include the following steps:

[0263] Step 701: Send indication information to the terminal device. The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET. The frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups. The frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0264] In this embodiment, the network device sends indication information to the terminal device, which instructs the terminal device to determine the frequency domain resources occupied by the control resource set CORESET. The terminal device can determine the frequency domain resources occupied by CORESET based on the indication information.

[0265] As one implementation of this application, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units.

[0266] In some implementations, the terminal device can determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET based on the indication information, thereby determining the frequency domain resources occupied by the CORESET.

[0267] In some implementations, the terminal device can obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol, and determine the size of the frequency domain resources occupied by the CORESET based on the indication information, thereby determining the frequency domain resources occupied by the CORESET.

[0268] In some implementations, the terminal device can obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol, and determine the highest aggregation level and the number of time domain symbols of the terminal device according to the indication information. Furthermore, based on the highest aggregation level and the number of time domain symbols of the terminal device, the size of the frequency domain resources occupied by the CORESET is determined, thereby determining the frequency domain resources occupied by the CORESET.

[0269] In some implementations, the size of the frequency domain resources occupied by the CORESET can also be determined based on the highest aggregation level of the terminal device, the number of PDCCH candidate channels supported by the highest aggregation level, and the number of time domain symbols.

[0270] Optionally, the size of the frequency domain resource can be matched with the bandwidth supported by the terminal device to avoid resource waste.

[0271] It is understood that in the embodiments of this application, the bandwidth supported by the terminal device can be either full bandwidth or partial bandwidth (BWP).

[0272] As another implementation of this application, the frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to one of at least two granularities.

[0273] In some implementations, the indication information includes at least 1 bit, which indicates the position of the at least one group of frequency domain resource units in a plurality of frequency domain resource units configured in the network device, and each bit of the indication information indicates whether the corresponding group of frequency domain resource units is a frequency domain resource occupied by the CORESET.

[0274] Frequency domain resource units can be resource blocks (RB), physical resource blocks (PRB), virtual resource blocks (VRB), common resource blocks (CRB), etc.

[0275] In some implementations, the granularity is determined based on at least one of the following: granularity indication information; bandwidth supported by the terminal device; number of bits of the indication information; number of resource particle groups (REGs) occupied by the control channel unit (CCE); and number of time-domain symbols configured by the network device. This allows for flexible configuration of the allocation granularity according to actual conditions, further improving resource utilization and avoiding resource waste.

[0276] In some implementations, releasing the remaining REGs in response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE) can further improve resource utilization and avoid resource waste.

[0277] In this embodiment of the application, if the control resource set CORESET is CORESET#0, then the first indication information is the Remaining Minimum System Message (RMSI). The RMSI signaling is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0278] In summary, by sending indication information to the terminal device, which is used to determine the frequency domain resources occupied by the control resource set CORESET, the frequency domain resources occupied by the CORESET are either contiguous frequency domain resource units or non-contiguous frequency domain resource units grouped together. These frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least two granularities. By changing the allocation method of the terminal device's frequency domain resources or flexibly configuring the allocation granularity of the frequency domain resources, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0279] Corresponding to the frequency domain resource configuration methods provided in the above embodiments, this application also provides a frequency domain resource configuration device. Since the frequency domain resource configuration device provided in this application corresponds to the methods provided in the above embodiments, the implementation of the frequency domain resource configuration method is also applicable to the frequency domain resource configuration device provided in the following embodiments, which will not be described in detail in the following embodiments.

[0280] Please see Figure 8 , Figure 8 This is a schematic diagram of a frequency domain resource configuration device provided in an embodiment of this application.

[0281] like Figure 8 As shown, the frequency domain resource configuration device 800 includes: a transceiver unit 810 and a processing unit 820, wherein:

[0282] The transceiver unit 810 is used to receive indication information sent by the network device;

[0283] Processing unit 820 is configured to determine the frequency domain resources occupied by the control resource set CORESET based on the indication information;

[0284] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0285] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0286] Optionally, the processing unit 820 is specifically used for:

[0287] Based on the indicated information, determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

[0288] Optionally, the processing unit 820 is specifically used for:

[0289] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0290] Based on the indicated information, determine the size of the frequency domain resources occupied by the CORESET;

[0291] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0292] Optionally, the processing unit 820 is specifically used for:

[0293] Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol;

[0294] The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device;

[0295] The size of the frequency domain resources occupied by the CORESET is determined based on the highest aggregation level of the terminal device and the number of time domain symbols; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time domain symbols.

[0296] The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

[0297] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0298] Optionally, the processing unit 820 is further configured to:

[0299] In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0300] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0301] Optionally, the granularity is determined based on at least one of the following:

[0302] Particle size indication information;

[0303] The bandwidth supported by the terminal device;

[0304] The number of bits in the indication information;

[0305] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0306] The number of time-domain symbols configured in the network device.

[0307] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0308] The frequency domain resource configuration device in this embodiment can receive indication information sent by a network device and determine the frequency domain resources occupied by the control resource set CORESET based on the indication information. The frequency domain resources occupied by the CORESET are either continuous frequency domain resource units or non-contiguous frequency domain resource units (groups of at least two frequency domain resource units). These frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least two granularities. By changing the allocation method of the terminal device's frequency domain resources or flexibly configuring the allocation granularity of the frequency domain resources, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0309] Please see Figure 9 , Figure 9 This is a schematic diagram of a frequency domain resource configuration device provided in an embodiment of this application.

[0310] like Figure 9 As shown, the frequency domain resource configuration device 900 includes: a transceiver unit 910, wherein:

[0311] The transceiver unit 910 is used to send instruction information to the terminal device;

[0312] The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET;

[0313] Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or,

[0314] The frequency domain resources occupied by the CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities.

[0315] Optionally, the indication information is used to determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET;

[0316] The starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources are used to determine the frequency domain resources occupied by the CORESET.

[0317] Optionally, the indication information is used to determine the size of the frequency domain resources occupied by the CORESET;

[0318] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0319] Optionally, the indication information is used to indicate the highest aggregation level of the terminal device and the number of time-domain symbols;

[0320] The highest aggregation level and the number of time-domain symbols of the terminal device are used to determine the size of the frequency domain resources occupied by the CORESET; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time-domain symbols.

[0321] The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

[0322] Optionally, the indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

[0323] Optionally, in response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

[0324] Optionally, the size of the frequency domain resources is matched with the bandwidth supported by the terminal device.

[0325] Optionally, the granularity is determined based on at least one of the following:

[0326] Particle size indication information;

[0327] The bandwidth supported by the terminal device;

[0328] The number of bits in the indication information;

[0329] The number of resource particles (REGs) occupied by the control channel unit (CCE);

[0330] The number of time-domain symbols configured in the network device.

[0331] Optionally, the control resource set CORESET is CORESET#0, the indication information is Minimum Residual System Message (RMSI), and the indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

[0332] The frequency domain resource configuration device in this embodiment can send indication information to the terminal device to determine the frequency domain resources occupied by the control resource set CORESET. The frequency domain resources occupied by the CORESET are either consecutive frequency domain resource units or non-consecutive frequency domain resource units (groups of at least two frequency domain resource units). These frequency domain resource unit groups are obtained by dividing multiple frequency domain resource units according to at least two granularities. By changing the allocation method of the terminal device's frequency domain resources or flexibly configuring the allocation granularity of the frequency domain resources, the terminal device can support higher aggregation levels as much as possible, effectively improving the transmission performance of the downlink channel, enhancing the coverage of the downlink channel, improving system communication efficiency, effectively reducing resource waste, and improving resource utilization.

[0333] To implement the above embodiments, this application also proposes a communication device, including: a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory to cause the device to perform... Figures 2 to 6 The method shown in the embodiment.

[0334] To implement the above embodiments, this application also proposes a communication device, including: a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory to cause the device to perform... Figure 7 The method shown in the embodiment.

[0335] To implement the above embodiments, this application also proposes a communication device, including: a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions to perform... Figures 2 to 6 The method shown in the embodiment.

[0336] To implement the above embodiments, this application also proposes a communication device, including: a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions to perform... Figure 7 The method shown in the embodiment.

[0337] Please see Figure 10 , Figure 10 This is a schematic diagram of another frequency domain resource configuration device provided in this embodiment. The frequency domain resource configuration device 1000 can be a network device, a terminal device, a chip, chip system, or processor that supports the network device in implementing the above methods, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0338] The frequency domain resource configuration device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the frequency domain resource configuration device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0339] Optionally, the frequency domain resource configuration device 1000 may further include one or more memories 1002, on which a computer program 1003 may be stored. The processor 1001 executes the computer program 1003 to cause the frequency domain resource configuration device 1000 to perform the method described in the above method embodiments. The computer program 1003 may be embedded in the processor 1001, in which case the processor 1001 may be implemented in hardware.

[0340] Optionally, the memory 1002 may also store data. The frequency domain resource configuration device 1000 and the memory 1002 can be configured separately or integrated together.

[0341] Optionally, the frequency domain resource configuration device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transceiver function. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0342] Optionally, the frequency domain resource configuration device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions to cause the frequency domain resource configuration device 1000 to perform the method described in the above method embodiments.

[0343] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0344] In one implementation, the frequency domain resource configuration device 1000 may include circuitry that can perform the functions of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0345] The frequency domain resource configuration device described in the above embodiments can be a network device or a terminal device, but the scope of the frequency domain resource configuration device described in this disclosure is not limited to this, and the structure of the frequency domain resource configuration device is not limited to this. Figures 8-9 The frequency domain resource configuration device can be a standalone device or part of a larger device. For example, a frequency domain resource configuration device could be:

[0346] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0347] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0348] (3) ASIC, such as modem;

[0349] (4) Modules that can be embedded in other devices;

[0350] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0351] (6) Others, etc.

[0352] For cases where the frequency domain resource configuration device can be a chip or a chip system, please refer to [link / reference]. Figure 11 The diagram shows the structure of the chip. Figure 11 The chip shown includes a processor 1101 and an interface 1102. There can be one or more processors 1101, and multiple interfaces 1102.

[0353] For cases where the chip is used to implement the functions of the network device in the embodiments of this disclosure:

[0354] Interface 1102 is used for code instructions and their transmission to the processor;

[0355] Processor 1101 is used to run code instructions to perform, such as Figures 2 to 6 The method.

[0356] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0357] Interface 1102 is used for code instructions and their transmission to the processor;

[0358] Processor 1101 is used to run code instructions to perform, such as Figure 7 The method.

[0359] Optionally, the chip also includes a memory 1103 for storing necessary computer programs and data.

[0360] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0361] This disclosure also provides a communication system, which includes the aforementioned... Figures 8-9The embodiments include a frequency domain resource configuration device as a terminal device and a frequency domain resource configuration device as a network device; alternatively, the system includes the aforementioned... Figure 10 The embodiments include a frequency domain resource configuration device as a terminal device and a frequency domain resource configuration device as a network device.

[0362] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0363] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0364] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs. When a computer program is loaded and executed on a computer, it generates, in whole or in part, the flow or function according to the embodiments of this disclosure. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0365] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0366] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0367] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0368] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0369] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0370] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0371] It should be understood that the various forms of processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the embodiments of this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this invention can be achieved, and this is not limited herein.

[0372] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A frequency domain resource allocation method, characterized in that, The method is executed by a terminal device, and the method includes: Receive instruction information sent by network devices; Based on the indicated information, determine the frequency domain resources occupied by the control resource set CORESET; Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, The frequency domain resources occupied by CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities. The size of the frequency domain resources is matched with the bandwidth supported by the terminal device; The control resource set CORESET is CORESET#0, and the indication information is Minimum Residual System Message (RMSI). The indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

2. The method according to claim 1, characterized in that, The step of determining the frequency domain resources occupied by the control resource set CORESET according to the indication information includes: Based on the indicated information, determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

3. The method according to claim 1, characterized in that, The step of determining the frequency domain resources occupied by the control resource set CORESET according to the indication information includes: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol; Based on the indicated information, determine the size of the frequency domain resources occupied by the CORESET; The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

4. The method according to claim 1, characterized in that, The step of determining the frequency domain resources occupied by the control resource set CORESET according to the indication information includes: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol; The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device; The size of the frequency domain resources occupied by the CORESET is determined based on the highest aggregation level of the terminal device and the number of time domain symbols; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time domain symbols. The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

5. The method according to claim 1, characterized in that, The indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

7. The method according to claim 5, characterized in that, The granularity is determined based on at least one of the following: Particle size indication information; The bandwidth supported by the terminal device; The number of bits in the indication information; The number of resource particles (REGs) occupied by the control channel unit (CCE); The number of time-domain symbols configured in the network device.

8. A frequency domain resource allocation method, characterized in that, The method is performed by a network device, and the method includes: Send instruction information to the terminal device; The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET; Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, The frequency domain resources occupied by CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities. The size of the frequency domain resources is matched with the bandwidth supported by the terminal device; The control resource set CORESET is CORESET#0, and the indication information is Minimum Residual System Message (RMSI). The indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

9. The method according to claim 8, characterized in that, The indication information is used to determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

10. The method according to claim 8, characterized in that, The indication information is used to determine the size of the frequency domain resources occupied by the CORESET; The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

11. The method according to claim 8, characterized in that, The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device; The highest aggregation level and the number of time-domain symbols of the terminal device are used to determine the size of the frequency domain resources occupied by the CORESET; The size of the frequency domain resources is functionally related to the highest aggregation level of the terminal device and the number of time domain symbols. The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

12. The method according to claim 8, characterized in that, The indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

13. The method according to any one of claims 8-12, characterized in that, The method further includes: In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

14. The method according to claim 12, characterized in that, The granularity is determined based on at least one of the following: Particle size indication information; The bandwidth supported by the terminal device; The number of bits in the indication information; The number of resource particles (REGs) occupied by the control channel unit (CCE); The number of time-domain symbols configured in the network device.

15. A frequency domain resource allocation device, characterized in that, The device is used in a terminal device, and the device includes: The transceiver unit is used to receive instruction information sent by network devices; The processing unit is configured to determine the frequency domain resources occupied by the control resource set CORESET based on the indication information. Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, The frequency domain resources occupied by CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities. The size of the frequency domain resources is matched with the bandwidth supported by the terminal device; The control resource set CORESET is CORESET#0, and the indication information is Minimum Residual System Message (RMSI). The indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

16. The apparatus according to claim 15, characterized in that, The processing unit is specifically used for: Based on the indicated information, determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

17. The apparatus according to claim 15, characterized in that, The processing unit is specifically used for: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol; Based on the indicated information, determine the size of the frequency domain resources occupied by the CORESET; The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

18. The apparatus according to claim 15, characterized in that, The processing unit is specifically used for: Obtain the starting position of the frequency domain resources occupied by the CORESET as specified in the protocol; The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device; The size of the frequency domain resources occupied by the CORESET is determined based on the highest aggregation level of the terminal device and the number of time domain symbols; the size of the frequency domain resources has a functional relationship with the highest aggregation level of the terminal device and the number of time domain symbols. The frequency domain resources occupied by the CORESET are determined based on the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources.

19. The apparatus according to claim 15, characterized in that, The indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

20. The apparatus according to any one of claims 15-19, characterized in that, The processing unit is also used for: In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

21. The apparatus according to claim 19, characterized in that, The granularity is determined based on at least one of the following: Particle size indication information; The bandwidth supported by the terminal device; The number of bits in the indication information; The number of resource particles (REGs) occupied by the control channel unit (CCE); The number of time-domain symbols configured in the network device.

22. A frequency domain resource allocation device, characterized in that, The device is used in a network device, and the device includes: The transceiver unit is used to send instruction information to the terminal device; The indication information is used to determine the frequency domain resources occupied by the control resource set CORESET; Wherein, the frequency domain resources occupied by the CORESET are continuous frequency domain resource units; or, The frequency domain resources occupied by CORESET are at least two non-contiguous frequency domain resource unit groups, which are obtained by dividing multiple frequency domain resource units according to at least one of two granularities. The size of the frequency domain resources is matched with the bandwidth supported by the terminal device; The control resource set CORESET is CORESET#0, and the indication information is Minimum Residual System Message (RMSI). The indication information is used to determine the frequency domain resource length and the corresponding number of symbols of CORESET#0 from at least one combination of frequency domain resource length and corresponding number of symbols agreed upon in the protocol.

23. The apparatus according to claim 22, characterized in that, The indication information is used to determine the starting position of the frequency domain resources occupied by the CORESET and the size of the frequency domain resources occupied by the CORESET.

24. The apparatus according to claim 22, characterized in that, The indication information is used to determine the size of the frequency domain resources occupied by the CORESET; The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

25. The apparatus according to claim 22, characterized in that, The indication information is used to indicate the highest aggregation level and the number of time-domain symbols of the terminal device; The highest aggregation level and the number of time-domain symbols of the terminal device are used to determine the size of the frequency domain resources occupied by the CORESET; The size of the frequency domain resources is functionally related to the highest aggregation level of the terminal device and the number of time domain symbols. The size of the frequency domain resources occupied by the CORESET is used to determine the frequency domain resources occupied by the CORESET.

26. The apparatus according to claim 22, characterized in that, The indication information includes at least one bit, which is used to indicate the position of the at least one frequency domain resource unit group among the plurality of frequency domain resource units configured in the network device.

27. The apparatus according to any one of claims 22-26, characterized in that, The device further includes: In response to the existence of remaining resource particle groups (REGs) not mapped to the control channel unit (CCE), the remaining REGs are released.

28. The apparatus according to claim 26, characterized in that, The granularity is determined based on at least one of the following: Particle size indication information; The bandwidth supported by the terminal device; The number of bits in the indication information; The number of resource particles (REGs) occupied by the control channel unit (CCE); The number of time-domain symbols configured in the network device.

29. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 7.

30. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 8 to 14.

31. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 1 to 7.

32. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 8 to 14.

33. A computer-readable storage medium for storing instructions that, when executed, cause the method as described in any one of claims 1 to 7 to be implemented.

34. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 8 to 14 to be implemented.

Images