CN115696591A

CN115696591A - Resource determination method and communication device

Info

Publication number: CN115696591A
Application number: CN202110876860.1A
Authority: CN
Inventors: 张战战; 铁晓磊; 花梦; 周涵; 黄雯雯
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-07-31
Filing date: 2021-07-31
Publication date: 2023-02-03
Also published as: WO2023011025A1

Abstract

The application provides a resource determination method and a communication device, which relate to the technical field of communication.A terminal device determines a frequency offset and a frequency position of a first resource, wherein the first resource is a bandwidth part BWP or a first control resource set CORESET; the frequency offset represents the frequency offset of a second CORESET relative to the first resource, and the first CORESET and the second CORESET do not overlap in a frequency domain; and determining the frequency position of a second CORESET according to the frequency position and the frequency offset of the first resource, and monitoring a physical downlink control channel PDCCH on the second CORESET. The terminal equipment determines the frequency position of the second CORESET through the method, interactive signaling between the terminal equipment and the network equipment is less, and signaling resources can be saved.

Description

Resource determination method and communication device

Technical Field

The embodiment of the application relates to the technical field of communication, and in particular relates to a resource determination method and a communication device.

Background

When a terminal device needs to access a New Radio (NR) network of a fifth generation mobile communication technology (5G), it needs to perform cell search, obtain system information, perform random access, and the like to better receive a communication service of the NR network of 5G.

Generally, in an initial access phase, a network device configures a control resource set (core set) #0 for the terminal device through a Master Information Block (MIB) so as to send a Physical Downlink Control Channel (PDCCH) to schedule a system message, a paging message, or data in a random access process. However, as the capacity of the communication system is continuously expanded, in order to balance the load, reduce the data congestion and achieve better communication performance, a new CORESET may be additionally introduced. In addition, the network device may configure more than one initial downlink bandwidth part (BWP) in the initial access phase, different initial downlink BWPs may not overlap with each other, and the newly configured initial downlink BWP may not include a synchronization signal/physical broadcast channel block (SSB) in the frequency domain, and the newly configured initial downlink BWP may also need to configure a new core. The CORESET newly configured outside CORESET #0 in the initial access stage may be farther from the SSB in the frequency domain, and determining the frequency domain position of the new CORESET by using the offset value based on the SSB requires a large number of newly defined offset values, which is low in accuracy and requires a large signaling overhead. There is also a part of CORESET that directly indicates the frequency domain position through a bitmap, but the signaling overhead of indicating the frequency domain position of CORESET through the bitmap is large.

Disclosure of Invention

The application provides a resource determining method and a communication device, which are used for determining the position of a resource under the condition of less signaling overhead.

In a first aspect, the present application provides a resource determining method, which may be executed by a terminal device or a network device, where the terminal device may be a User Equipment (UE), a vehicle-mounted device, a smart watch, a smart band, and the network device may be a Transmission Reception Point (TRP), a 5G base station (gnodeB, gNB), and the like, and the present application is not limited specifically herein. Upon execution:

the network device may determine a frequency location of a first resource and a frequency location of a second CORESET, the first resource being BWP or the first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; the first core set may be configured by system information, such as a Master Information Block (MIB) or a system information block 1 (sib1), for example, the first core set is core set #0 configured by MIB; the network equipment can determine the frequency offset of the second CORESET relative to the first resource according to the frequency position of the first resource and the frequency position of the second CORESET; the network equipment informs the terminal equipment of the frequency position and the frequency offset of the first resource; the terminal equipment determines the frequency position of a second CORESET according to the frequency position and the frequency offset of the first resource; and the network equipment sends the PDCCH in the second CORESET, and the terminal equipment monitors the PDCCH in the second CORESET.

When the first resource is a BWP, the first resource may be an uplink BWP or a downlink BWP, may be a Radio Resource Control (RRC) IDLE (IDLE) or RRC INACTIVE (INACTIVE) resource, and may also be a RRC CONNECTED (CONNECTED) resource, which is not limited specifically herein. The first CORESET may be a control resource set CORESET #0 identified as 0 configured by the network device for the terminal device, or may be another identified control resource set, which is not specifically limited herein. The first resource may be configured by System Information (SI), for example, SIB1, or configured by another RRC message, for example, configured by an RRC message in an RRC connected state, and is not particularly limited herein. As more and more terminals are accessed in the communication system, a plurality of CORESET can be reintroduced to improve the communication service quality for load balancing. The introduced CORESET can be a second CORESET, wherein the second CORESET and the first CORESET are not overlapped in a frequency domain, so that better communication service quality can be ensured, the system capacity is improved, and the problem of PDCCH congestion is solved.

In addition, the frequency position may also be referred to as a frequency domain position, and specific names are not specifically limited herein, and may be determined according to specific application scenarios in actual applications.

The second CORESET is introduced to balance load and expand system capacity, the terminal device determines the second CORESET based on the first resource and the frequency deviation, and compared with the method for determining the frequency position of the CORESET through the bit bitmap indication, signaling overhead can be reduced, time-frequency resources are saved, and resource utilization efficiency is improved.

In an alternative approach, the frequency offset represents: an offset of a first resource block RB of the second CORESET from a first RB of the first resource; or, the offset of the last RB of the second CORESET relative to the last RB of the first resource; or, the offset of the center RB of the second CORESET from the center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of the upper boundary of the second CORESET relative to the upper boundary of the first resource; or, an offset of a center frequency of a first resource element, RE, of a first RB of a second CORESET from a center frequency of a first RE of a first RB of a first resource; or, an offset of a center frequency of a first resource element RE of a last RB of a second CORESET from a center frequency of a first RE of a last RB of a first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the lower boundary of the second CORESET is offset from the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

It should be noted that, in practical applications, the frequency offset specifically indicates which frequency position of the first resource and which frequency position of the second core set are offset between, which may be determined according to service requirements, and is not specifically limited herein.

In an alternative mode, the terminal device may receive indication information from the network device, where the indication information is used to indicate a frequency offset; the indication information is one or more of the following signaling:

SIB1, downlink Control Information (DCI) for scheduling SIB1, and MIB. By adopting the signaling, the terminal equipment can acquire the frequency offset after acquiring the DCI/MIB of the SIB 1/scheduling SIB1 in the initial access stage, and the determination of the frequency position of the second CORESET in the initial access stage is facilitated, so that the load balance can be realized in the initial access stage, and the congestion of the PDCCH is reduced.

In an optional manner, the indication information is further used to indicate a bandwidth of the second core set and a number of OFDM symbols of the second core set. Therefore, the bandwidth of the second CORESET and the number of OFDM symbols of the second CORESET can be determined more flexibly. In addition, optionally, the indication information may be used to determine the bandwidth, the number of symbols, and the frequency offset of the second core set at the same time, so that signaling overhead may be saved, and it is not necessary to indicate the bandwidth, the number of symbols, and the frequency offset of the second core set separately.

In an alternative mode, the second CORESET is configured the same as CORESET #0 except for the frequency location, CORESET #0 is configured by the system information, and the configuration except for the frequency location includes at least one of the following:

bandwidth, orthogonal Frequency Division Multiplexing (OFDM) symbol number, control channel element and resource element group mapping type (control channel element resource mapping type, cce-REG-mapping type), resource element group size (REG-bundling), interleaver size (interleaver), precoding granularity (precoding granularity), and demodulation reference signal scrambling Identity (physical downlink control channel scrambling Identity) of PDCCH. In this way, the parameter of the second CORESET may multiplex the parameter of CORESET #0, and there is no need to separately configure the parameter of the second CORESET, which may save signaling overhead, especially when the second CORESET is configured in the initial access phase, signaling overhead in the initial access phase may be saved, for example, signaling overhead of SIB1 may be saved.

In an alternative manner, the configuration of the second CORESET associated search space set is the same as the configuration of the CORESET #0 associated search space set, CORESET #0 is configured by the system information, and the configuration of the search space set includes at least one of the following:

monitoring period, period offset, the number of continuous time slots of each monitoring occasion, monitoring symbols in the monitoring occasions, candidate PDCCH aggregation level, the number of PDCCH candidates corresponding to the candidate PDCCH aggregation level, search space set type and search space associated DCI format. In this way, the parameters of the search space set associated with the second CORESET may multiplex the parameters of the search space set associated with CORESET #0, and there is no need to separately configure the parameters of the search space set associated with the second CORESET, which may save signaling overhead, especially when the second CORESET is configured in the initial access phase, signaling overhead in the initial access phase may be saved, for example, signaling overhead of SIB1 may be saved.

In a second aspect, the present application provides a resource determining method, which may be executed by a terminal device, and may also be executed by a network device, where the terminal device may be a UE, an in-vehicle device, a smart watch, a smart bracelet, and the like, and the network device may be a TRP, a gNB, and the like, and the present application is not limited specifically herein. Upon execution:

the network device can determine a frequency position of a first resource and a frequency position of a second CORESET, wherein the first resource is a bandwidth part BWP or a first control resource set CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; the first core set can be configured by the system information, for example, by MIB or SIB1, for example, the first core set is core set #0 configured by MIB, and the network device notifies the terminal device of the frequency location of the first resource; the terminal equipment determines the frequency position of a second CORESET according to the frequency position of the first resource; and the network equipment sends the PDCCH in the second CORESET, and the terminal equipment monitors the PDCCH in the second CORESET.

The first CORESET may be a control resource set CORESET #0 identified as 0 configured by the network device for the terminal device, or may be another identified control resource set, which is not specifically limited herein. As more and more terminals are accessed in the communication system, a plurality of CORESET can be reintroduced to improve the communication service quality for load balancing. The introduced CORESET may be a second CORESET, wherein the second CORESET does not overlap or partially does not overlap the first CORESET to ensure better communication service quality. In addition, the frequency position may also be referred to as a frequency domain position, and specific names are not specifically limited herein, and may be determined according to specific application scenarios in actual applications.

It should be noted that, in this scheme, the network device and the terminal device may agree in advance that there is no offset between the frequency location of the first resource and the frequency location of the second core set, or the offset is a fixed value, so that the terminal device may determine the frequency location of the second core set directly according to the frequency location of the first resource, which is more convenient and faster.

In an alternative approach, the first resource block RB of the second CORESET is aligned with the first RB of the first resource; or, the last RB of the second CORESET is aligned with the last RB of the first resource; or, the center RB of the second CORESET is aligned with the center RB of the first resource; or, the lower boundary of the second CORESET is aligned with the lower boundary of the first resource; or, the upper boundary of the second CORESET is aligned with the upper boundary of the first resource; or, a center frequency of a first resource element, RE, of a first RB of a second CORESET is aligned with a center frequency of a first RE of the first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is aligned with the center frequency of the first RE of the last RB of the first resource; or, the upper boundary of the second CORESET is aligned with the preset frequency of the first resource; or, the lower boundary of the second CORESET is aligned with the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

The above alignment may be understood as a frequency offset of 0 or a fixed value, for example, the alignment of the first resource block RB of the second core set with the first RB of the first resource may be understood as that there is no frequency offset between the first resource block RB of the second core set and the first RB of the first resource, or the frequency offset between the first resource block RB of the second core set and the first RB of the first resource is a fixed value.

bandwidth, number of OFDM symbols, cci-REG-MappingType, resource element group size (REG-bundlesize), interleaver size (interleaver), precoding granularity (precoding granularity), and pdcch-DMRS-ScramblingID.

In an alternative manner, the configuration of the second CORESET associated search space set is the same as the configuration of the CORESET #0 associated search space set, the CORESET #0 is configured by the system information, and the configuration of the search space set includes at least one of the following:

monitoring period, period offset, the number of continuous time slots of each monitoring occasion, monitoring symbols in the monitoring occasions, candidate PDCCH aggregation level, the number of PDCCH candidates corresponding to the candidate PDCCH aggregation level, search space set type and search space associated DCI format.

In a third aspect, the present application provides a communication apparatus, which may be understood as a terminal device, may be a UE, a vehicle-mounted device, a smart watch, a smart bracelet, and the like, and includes: a processing unit and an input-output unit.

The processing unit is used for determining a frequency offset and a frequency position of a first resource, wherein the first resource is a bandwidth part BWP or a first control resource set CORESET; the frequency offset represents a frequency offset of the second CORESET relative to the first resource, and the first CORESET and the second CORESET do not overlap in a frequency domain; determining the frequency position of a second CORESET according to the frequency position and the frequency offset of the first resource; and the input and output unit is used for monitoring a physical downlink control channel PDCCH in the second CORESET.

In an alternative approach, the frequency offset may represent: an offset of a first resource block RB of the second CORESET from a first RB of the first resource; or, the offset of the last RB of the second CORESET relative to the last RB of the first resource; or, the offset of the center RB of the second CORESET from the center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, an offset of a center frequency of a first resource element, RE, of a first RB of a second CORESET from a center frequency of a first RE of a first RB of a first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the lower boundary of the second CORESET is offset from the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

In an optional mode, the input-output unit is further configured to: receiving indication information, wherein the indication information is used for indicating frequency offset; the indication information is one or more of the following signaling:

SIB1, DCI scheduling SIB1, and MIB.

In an optional manner, the indication information is further used to indicate a bandwidth of the second core set and a number of OFDM symbols of the second core set.

In a fourth aspect, the present application provides a communication apparatus, which may be understood as a network device, and may be a TRP, a gNB, and the like, including: a processing unit and an input-output unit.

The processing unit is used for determining the frequency position of a first resource and the frequency position of a second control resource set CORESET, wherein the first resource is BWP or first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; determining a frequency offset according to the frequency position of the first resource and the frequency position of the second CORESET; the frequency offset represents a frequency offset of the second CORESET relative to the first resource; an input-output unit for notifying the terminal device of the frequency location and the frequency offset of the first resource; and transmitting a Physical Downlink Control Channel (PDCCH) at a second CORESET.

In an alternative approach, the frequency offset may represent: an offset of a first resource block RB of the second CORESET from a first RB of the first resource; or, the offset of the last RB of the second CORESET relative to the last RB of the first resource; or, the offset of the center RB of the second CORESET from the center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, an offset of a center frequency of a first resource element, RE, of a first RB of a second CORESET from a center frequency of a first RE of a first RB of a first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the deviation of the lower boundary of the second CORESET from the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

In an alternative approach, the frequency offset is indicated by one or more of the following signaling:

SIB1, DCI scheduling SIB1, and MIB.

In an optional manner, the signaling is further used to indicate a bandwidth of the second core set and a number of OFDM symbols of the second core set.

bandwidth, number of OFDM symbols, cae-REG-MappingType, resource element group size (REG-bundling), interleaver size (interleaver), precoding granularity (precoding granularity), and pdcch-DMRS-scrimblingid.

In a fifth aspect, the present application provides a communication apparatus, which can be understood as a terminal device, and can be a UE, an in-vehicle device, a smart watch, a smart bracelet, and the like, including: a processing unit and an input-output unit.

The processing unit is used for determining the frequency position of the second CORESET according to the frequency position of the first resource; the first resource is BWP or first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; and the input and output unit is used for monitoring the PDCCH in the second CORESET.

In an alternative approach, the first resource block RB of the second CORESET is aligned with the first RB of the first resource; or, the last RB of the second CORESET is aligned with the last RB of the first resource; or, the center RB of the second CORESET is aligned with the center RB of the first resource; or, the lower boundary of the second CORESET is aligned with the lower boundary of the first resource; or, the upper boundary of the second CORESET is aligned with the upper boundary of the first resource; or, the center frequency of the first resource element RE of the first RB of the second CORESET is aligned with the center frequency of the first RE of the first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is aligned with the center frequency of the first RE of the last RB of the first resource; or, the upper boundary of the second CORESET is aligned with the preset frequency of the first resource; or, the lower boundary of the second CORESET is aligned with the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

In a sixth aspect, the present application provides a communication apparatus, which may be understood as a network device, and may be a TRP, a gNB, and the like, including: a processing unit and an input-output unit.

The processing unit is used for determining the frequency position of a first resource and the frequency position of a second CORESET, wherein the first resource is BWP or the first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; and the input and output unit is used for informing the terminal equipment of the frequency position of the first resource and sending the PDCCH in the second CORESET.

In an alternative, the first resource block RB of the second CORESET is aligned with the first RB of the first resource; or, the last RB of the second CORESET is aligned with the last RB of the first resource; or, the center RB of the second CORESET is aligned with the center RB of the first resource; or, the lower boundary of the second CORESET is aligned with the lower boundary of the first resource; or, the upper boundary of the second CORESET is aligned with the upper boundary of the first resource; or, the center frequency of the first resource element RE of the first RB of the second CORESET is aligned with the center frequency of the first RE of the first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is aligned with the center frequency of the first RE of the last RB of the first resource; or, the upper boundary of the second CORESET is aligned with the preset frequency of the first resource; or, the lower boundary of the second CORESET is aligned with the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

In an alternative, the second CORESET is the same as CORESET #0 except for the frequency location, CORESET #0 is configured by the system information, and the configuration except for the frequency location includes at least one of:

In a seventh aspect, the present application provides a communications apparatus comprising at least one processor and a memory; the memory is for storing a computer program or instructions which, when executed by the apparatus, are executable by the at least one processor to cause the communication apparatus to perform the method of the first aspect or embodiments of the first aspect as described above or the method of the second aspect or embodiments of the second aspect.

In an eighth aspect, the present application provides another communication device, comprising: an interface circuit and a logic circuit; where interface circuitry may be understood as an input-output interface, logic circuitry may be used to execute the code instructions to perform the methods of the first aspect or embodiments of the first aspect or the second aspect or embodiments of the second aspect described above.

In a ninth aspect, the present application further provides a computer readable storage medium having computer readable instructions stored thereon which, when run on a computer, cause the computer to perform the method as in the first aspect or any one of the possible designs of the first aspect or the method as in the second aspect or any one of the possible designs of the second aspect.

In a tenth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or embodiments of the first aspect described above or the method of the second aspect or embodiments of the second aspect.

In an eleventh aspect, the present application provides a chip system, which includes a processor and may further include a memory, and is configured to implement the method described in the first aspect or any one of the possible designs of the first aspect or the method described in the second aspect or any one of the possible designs of the second aspect. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

In a twelfth aspect, the present application provides a communication system comprising a first communication device and a second communication device, the communication system being adapted to perform the method of the first aspect or any one of the possible designs of the first aspect or the method of the second aspect or any one of the possible designs of the second aspect.

For technical effects that can be achieved by the third aspect to the twelfth aspect, please refer to a description of the technical effects that can be achieved by the corresponding possible design schemes in the first aspect or the second aspect, and details are not repeated herein.

Drawings

Fig. 1 is a schematic diagram illustrating a communication system provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a CORESET #0 frequency location determination scenario;

fig. 3 is a flowchart illustrating a resource determination method according to an embodiment of the present application;

fig. 4A is a schematic diagram illustrating a frequency location determination scenario of CORESET # R according to an embodiment of the present application;

fig. 4B illustrates a flowchart of a resource determining method provided in an embodiment of the present application;

fig. 5 is a flowchart illustrating a resource determination method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 8 shows a schematic structural diagram of a communication device provided in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings. The particular methods of operation in the method embodiments may also be applied in device embodiments or system embodiments. In the description of the present application, the meaning of "a plurality" is two or more, unless otherwise specified. Therefore, the implementation of the apparatus and the method can be referred to each other, and repeated descriptions are omitted.

The present application is applicable to a 5G NR system, and also applicable to other communication systems, such as a next-generation communication system. As shown in fig. 1, the communication system is composed of a network device and UE1 to UE 6. In the communication system, the UE1 to the UE6 may send information to the network device, and the network device may receive the information sent by the UE1 to the UE6 and feed back a response message.

In addition, UE4 to UE6 may also form a communication system, in this case, the first communication device and the second communication device may also be both terminal devices, for example, in an internet of vehicles system, terminal device 1 sends configuration information to terminal device 2, and receives data sent by terminal device 2; and the terminal device 2 receives the configuration information transmitted by the terminal device 1 and transmits data to the terminal device 1.

The network device is a device deployed in a radio access network to provide a wireless communication function for a terminal device. The access network device has a device with wireless transceiving function or a chip that can be set in the device, and the device includes but is not limited to: evolved node B (eNB), base Station Controller (BSC), base Transceiver Station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), base Band Unit (BBU), access Point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP or transmission point, TP), etc., gNB in 5G (e.g., NR) system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of base station in 5G system, or a network node constituting gNB or transmission point, such as baseband unit (BBU), satellite, drone, etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may further include a Radio Unit (RU). The CU implements part of the function of the gNB, and the DU implements part of the function of the gNB, for example, the CU implements the function of an RRC, a Packet Data Convergence Protocol (PDCP) layer, and the DU implements the function of a Radio Link Control (RLC), a Media Access Control (MAC), and a Physical (PHY) layer. Since the information of the RRC layer eventually becomes (i.e., is transmitted through) or is converted from the information of the PHY layer, under such an architecture, higher layer signaling, such as RRC layer signaling or PDCP layer signaling, can also be considered to be transmitted by the DU or the DU + RU. It is to be understood that the access network device may be a CU node, or a DU node, or a device comprising a CU node and a DU node. In addition, the CU may be divided into network devices in the access network RAN, or may be divided into network devices in the core network CN, which is not limited herein.

The terminal device, which may also be referred to as a terminal, in this embodiment of the present application is an entity for receiving or transmitting a signal at a user side, and is configured to send an uplink signal to a network device or receive a downlink signal from the network device. Including devices that provide voice and/or data connectivity to a user and may include, for example, handheld devices having wireless connection capabilities or processing devices connected to wireless modems. The terminal device may communicate with a core network via a Radio Access Network (RAN), and may exchange voice and/or data with the RAN. The terminal device may include a UE, a V2X terminal device, a wireless terminal device, a mobile terminal device, a device-to-device communication (D2D) terminal device, a machine-to-machine/machine-type communication (M2M/MTC) terminal device, an internet of things (IoT) terminal device, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a remote station (remote station), an Access Point (AP), a remote terminal (remote), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), or user equipment (user device), a wearable device, an in-vehicle device, an unmanned aerial vehicle, and the like.

While the various terminal devices described above, if located on (e.g. placed in or installed in) a vehicle, may be considered to be vehicle-mounted terminal devices, also referred to as on-board units (OBUs), for example.

Currently, NR is discussing a new UE type, called reduced capability (RedCap) UE. The reccap UE may be wearable devices (radios), industrial wireless sensors (industrial wireless sensors), and Video surveillance (Video surveillance) devices. Currently, an NR enhanced mobile broadband (eMBB) UE supports a 100MHz bandwidth in FR1 and a 200MHz bandwidth in FR2, where FR1 and FR2 are FR1 frequency band and FR2 frequency band defined by the third generation partnership project (3 gpp). And the maximum bandwidth supported by NR red map UE in FR1 is 20MHz. In FR2, the maximum bandwidth supported by a RedCap UE is 100MHz. The reason why the bandwidth capability supported by the reccap UE is smaller than that of the eMBB UE is because the reccap UE is low in implementation complexity and power consumption.

In the initial access stage (such as power-on network access, airplane mode cancellation, random access, etc.), the network device configures a core set for the eMBB UE through MIB signaling, where the ID of the core set is 0, that is, core set #0. Furthermore, optionally, SIB1 signaling may configure the UE with 1 additional common CORESET, called common CORESET, whose ID is not 0, and which is to be located within the bandwidth range of CORESET #0 in the frequency domain.

To expand system capacity and balance load, the network device may configure the RedCap UE with a new CORESET (assuming that the CORESET is CORESET # R, which may also be referred to as CORESET #0A, or other numbered CORESET, and the name of the new CORESET is not specifically limited in this application).

It should be understood that a control resource set, i.e., CORESET, is defined in NR for transmitting PDCCH, one CORESET consisting of several RBs in frequency domain and 1, 2 or 3 OFDM symbols in time domain.

In a system where NR eMBB UE and NR retrieve UE coexist, regardless of eMBB UE or retrieve UE, downlink data in the initial access phase is transmitted in the initial downlink BWP, and for example, PDCCH for scheduling message 2 or message 4, paging PDCCH for scheduling paging message, etc. are transmitted in CORESET #0 in the random access procedure. As the number of eMBB UEs and reccap UEs increases, channel congestion, such as PDCCH congestion (PDCCH blocking), may be caused during an initial access phase. In order to improve system capacity and balance UE load, at least one new initial downlink BWP may be additionally configured for the recmap UE in addition to the existing initial downlink BWP for data transmission of the recmap UE.

In addition, in a Time Division Duplex (TDD) system, because the bandwidth capability of the eMBB UE is higher, for example, FR1 supports a radio frequency bandwidth capability of 100MHz. Therefore, the bandwidth of the initial uplink BWP configured by the network device for the eMBB UE may exceed the maximum bandwidth capability supported by the reccap UE. In order to support uplink transmission of a red map UE, data of the red map UE is within the bandwidth supported by the red map UE, a new initial uplink BWP may be configured for the red map UE, and the bandwidth of the new initial uplink BWP should not exceed the maximum bandwidth capability supported by the red map UE. In a TDD system, an upstream BWP and a downstream BWP form a BWP pair (BWP pair), which have the same ID and the same center frequency. For example, the initial upstream BWP and the initial downstream BWP are a BWP pair, and should have the same center frequency. However, the center frequency of the initial uplink BWP newly introduced to the redmap UE may not be aligned with the center frequency of the initial downlink BWP configured for the eMBB UE, and therefore, in addition to the reason of expanding the system capacity, in order to keep the center frequency point alignment of the initial uplink BWP of the redmap UE, an initial downlink BWP may be newly introduced to the redmap UE, which is referred to as: redCap-initial DL BWP.

However, at least one core set is generally configured in the initial downlink BWP configured for the red beacon UE, for example, the initial downlink BWP of the red beacon UE does not include core set #0, and at this time, a new core set is configured for the red beacon UE inside the initial downlink BWP of the red beacon UE.

Typically, the network device may indicate the bandwidth of core set #0, the number of symbols, the offset value between SSBs, etc., so that the terminal device may determine the frequency location of core set #0 based on the offset value between SSBs and core set #0 and the frequency location of SSBs. As shown in fig. 2, when initially accessing, the UE first searches for the SSB, where a MIB included in a Physical Broadcast Channel (PBCH) included in the SSB indicates an index value, and the index value is used to indicate a bandwidth, a symbol number, an offset value between the SSBs, and the like of the CORESET #0, and then, according to the offset value between the SSB and the CORESET #0, the UE may determine a frequency location of the CORESET #0, and further, according to a bandwidth corresponding to the index value, determine a bandwidth of the CORESET #0. The time interval between the SSB and the CORESET #0 is only for illustration, and for better illustration, the time interval is provided between the SSB and the CORESET #0, and is not particularly limited in practical application. However, the CORESET newly introduced for the recmap UE may be farther from the SSB in the frequency domain, or the initial downlink BWP configured for the recmap UE does not include the SSB, and the current offset value does not support the CORESET # R to be configured at a position farther from the SSB, so it is inappropriate to determine the frequency position of the CORESET # R based on the SSB.

In addition, the related art also proposes determining the frequency position of CORESET other than CORESET #0 by a bitmap (bitmap). In NR, one downlink BWP includes an integer number of RBs in the frequency domain, and CORESET may be a partial number of RBs in one BWP in the frequency domain, and one CORESET also includes an integer number of RBs. For example, a downlink BWP starts from the first RB in the frequency domain, and every 6 RBs are taken as an RB group (RB group), and the RB group where the first RB is located is referred to as the first RB group. The first bit of the bitmap corresponds to the first RB group in BWP, the second bit corresponds to the second RB group, and so on. If 1 bit is set to 1, the RB group corresponding to the bit is the frequency domain resource included by the CORESET, otherwise, the RB group corresponding to the bit does not belong to the CORESET. Considering CORESET # R, it is possible to carry configuration information of CORESET # R through SIB1 signaling. If the frequency location of CORESET # R is determined by the bitmap, the signaling overhead (load overhead) of SIB1 is increased. Wherein, the SIB1 signaling is a broadcast signaling and carries the minimum system message, and if the SIB1 signaling overhead is too large, the system resource utilization efficiency may be reduced.

In order to determine the frequency position of CORESET # R and the frequency positions of other CORESETs except CORESET #0 under the condition of low signaling overhead, the application provides a resource determination method. Specifically, the method may be executed by a terminal device, and may also be executed by a network device, where the terminal device may be a UE, an in-vehicle device, a smart watch, a smart bracelet, and the like, and the network device may be a TRP, a gNB, and the like, and the application is not limited specifically herein. In execution, referring to fig. 3, fig. 3 illustrates a terminal device as a UE and a network device as a gNB, but in actual application, the category of the terminal device and the category of the network device are not specifically limited:

step 301, the gNB determines the frequency position of a first resource and the frequency position of a second CORESET, wherein the first resource is BWP or the first CORESET; the first CORESET and the second CORESET do not overlap in the frequency domain.

When the first resource is a BWP, the first resource may be an uplink BWP or a downlink BWP, may be an RRC IDLE state BWP or an RRC INACTIVE state BWP, and may also be an RRC connected resource, which is not limited herein. The first core set may be configured by system information, for example, MIB or SIB 1. The first CORESET may be a control resource set CORESET #0 identified as 0 configured by the network device for the terminal device, or may be other identified control resource sets, which is not specifically limited herein. As more and more terminal devices are accessed in a communication system, for load balancing, a plurality of CORESETs can be introduced in the initial access stage to improve the communication service quality. The introduced core set may be a second core set, wherein the second core set does not overlap the first core set in the frequency domain, which may be understood as that the second core set does not overlap the first core set in the frequency domain, or partially does not overlap the first core set in the frequency domain, which may ensure better communication service quality. The second core set and the first core set may be configured for the same terminal device, for example, the first core set configured for the eMBB UE is core #0, and the second core set may be a common core set or other core set configured for the eMBB UE; the second core set and the first core set may also be configured for different terminal devices, for example, the first core set configured for the eMBB UE is core set #0, the second core set may be core set # R configured for the redtap UE, it should be understood that the redtap UE may also monitor the PDCCH on the first core set or the core set #0, and the first core set may also be core set # R configured for the redtap UE, and the second core set may be other core sets configured for the eMBB UE besides core set #0, and is not particularly limited herein.

It should be noted that, when the first resource is BWP, it may be an uplink BWP or a downlink BWP configured for the recap UE by the network device, for example, the first resource is an initial downlink BWP or an initial uplink BWP configured for the recap UE by the network device, and the network device may also configure a downlink BWP and an uplink BWP for the eMBB UE, and the frequency position and the bandwidth of the downlink/uplink BWP configured for the recap UE and the eMBB UE may be the same or different, which is not limited herein. In addition, the frequency position may also be referred to as a frequency domain position, and specific names are not specifically limited herein, and may be determined according to specific application scenarios in actual applications. Determining the frequency location of the first resource with reference to the red map downlink/uplink BWP helps to configure the core # R inside the red map downlink/uplink BWP, or to ensure that the total bandwidth of the red map downlink/uplink BWP and the core # R does not exceed the maximum bandwidth capability supported by the red map UE.

When the first resource is the first core set, the first core set can be core set #0, the method is simpler and faster, and the second core set can be configured not to overlap with the core set #0, so that the system capacity can be increased, and the PDCCH congestion can be reduced. In practical application, the first resource may be specifically which may be agreed by a protocol between the terminal device and the network device, or may be indicated by a signaling of the network device.

Step 302, the gNB determines a frequency offset of the second CORESET relative to the first resource according to the frequency location of the first resource and the frequency location of the second CORESET.

In an alternative manner, the frequency offset may represent: the offset of the first RB of the second CORESET from the first RB of the first resource may also be an offset of the first RB of the second CORESET from the last RB or center RB of the first resource. In addition, it is further noted that the RBs included in the second CORESET in the present application are continuous in the frequency domain.

It should be understood that when a block of frequency domain resource X includes an even number of RBs, its center RB is an RB above the center frequency of X that is adjacent to the center frequency, or an RB below the center frequency of X that is adjacent to the center frequency. For example, a BWP includes a total of 40 RBs, numbered from 0 to 39, then the center RB corresponds to either RB number 19 or RB number 20. The specific ones can be predefined by the protocol, or indicated by the network device. And when the number of RBs included in one frequency domain resource is odd, the central RB is the RB located at the central frequency domain position of the frequency domain resource. For example, a BWP includes 41 RBs numbered from 0 to 40, and the central RB corresponds to the RB numbered 20, and any description related to the central RB is referred to herein and will not be repeated herein.

The frequency offset may also represent an offset of the last RB of the second CORESET from the last RB of the first resource, and may also be an offset of the last RB of the second CORESET from the first RB or the center RB of the first resource.

The frequency offset may also represent an offset of the center RB of the second CORESET from the center RB of the first resource, and may also be an offset of the center RB of the second CORESET from the first RB or the last RB of the first resource.

The frequency offset may also represent an offset of the lower boundary of the second CORESET from the lower boundary of the first resource, and may also be an offset of the lower boundary of the second CORESET from the upper boundary or center frequency of the first resource. The lower boundary of a block of frequency domain resources Y represents the lower boundary of the first RE in the first RB of Y (the interval from the center frequency of the first RE is 1/2 × SCS, which is the subcarrier interval of the block of frequency domain resources), i.e., the frequency domain starting position of the block of resources. The upper bound of Y, represents the upper bound of the last RE in the last RB of Y (spaced 1/2 SCS from the center frequency of the last RE, which is the subcarrier spacing of the block of frequency domain resources), i.e., the frequency domain end location of this block of resources. Any description concerning the lower and upper boundaries below may be referred to herein and will not be repeated.

The frequency offset may also represent an offset of an upper boundary of the second CORESET from an upper boundary of the first resource, the upper boundary of the second CORESET being offset from a lower boundary or center frequency of the first resource.

The frequency offset may also represent an offset of an upper boundary of the second CORESET from a center frequency of the first resource, and may also be an offset of an upper boundary of the second CORESET from a lower boundary or an upper boundary of the first resource.

The frequency offset may also represent an offset of a center frequency of a first resource element RE of a first RB of the second CORESET relative to a center frequency of a first RE of a first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the center frequency of the last resource element RE of the last RB of the second CORESET is offset from the center frequency of the last RE of the last RB of the first resource.

The frequency offset may also represent an offset of an upper boundary of the second CORESET from a preset frequency of the first resource; or, the deviation of the lower boundary of the second CORESET from the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0. For example, the preset frequency of the first resource is a frequency point which deviates from the center frequency of the first resource by a certain frequency interval in the direction of increasing the RB number, and at this time, the frequency offset may be determined by using the upper boundary of the second CORESET, and the frequency offset may be determined by referring to the lower boundary and the center frequency of the second CORESET. For example, the preset frequency of the first resource is a frequency point which is deviated from the center frequency of the first frequency domain resource by a certain frequency interval in the direction of reducing the RB number, and at this time, the frequency deviation may be determined by the lower boundary of the second CORESET, and in addition, the frequency deviation may be determined by referring to the upper boundary and the center frequency of the second CORESET. Wherein the certain frequency interval comprises: 10MHz and 50MHz. For example, considering that the maximum bandwidth capability supported by the RedCap UE in FR1 is 20MHz, and the maximum bandwidth capability supported in FR2 is 100MHz, the certain frequency interval may be 10MHz in FR1, and 50MHz in FR 2. In this way, the frequency location of the second core set can be indicated more flexibly, and it can also be ensured that the total bandwidth of the red map downlink/uplink BWP and the second core set does not exceed the maximum bandwidth capability supported by the red map UE. According to this approach, the indicated second CORESET may not be completely included within the recmap upstream BWP. It should be understood that the UE does not expect the second CORESET to be partially or fully outside the reccap downlink BWP. That is, if a red map downstream BWP is configured, the second CORESET should be located completely inside the red map downstream BWP.

It should be noted that, the frequency domain offset may be represented by the number of RBs, the number of REs, or an absolute frequency (for example, in MHz or KHz), and is not specifically limited herein, and in actual application, the frequency offset specifically represents which frequency position of the first resource and which frequency position of the second CORESET are offset, and may be determined according to a service requirement or may be indicated according to a signaling of the network device, and is not specifically limited herein. It should be understood that even if the unit of frequency offset is expressed in terms of the number of RBs or REs, the specific frequency offset can be accurately determined by conversion to absolute frequency, for example, the number of RBs is converted to MHz, which requires knowing the subcarrier spacing used in the conversion, which can be indicated by the network device, such as RRC signaling, or predefined by the protocol. For example, the subcarrier spacing corresponding to the frequency domain offset is equal to the subcarrier spacing of the second CORESET, or equal to the subcarrier spacing of the first resource.

In addition, when the first resource is the first core set, if the frequency offset is determined based on the first RB of the first core set, the last RB of the second core set may be selected to determine the frequency offset, so as to ensure that the numbers of the first core set and the second core set do not overlap, and the number of the last RB of the second core set is less than or equal to the number of the first RB of the first core set, that is, the number of any RB of the second core set is less than or equal to the number of any RB of the first core set. Similarly, if the frequency offset is determined based on the last RB of the first CORESET, the first RB of the second CORESET may be selected to determine the frequency offset, which may ensure that the numbering of the first CORESET and the second CORESET does not overlap, and that the numbering of the first RB of the second CORESET is greater than or equal to the numbering of the first RB of the first CORESET, i.e., the numbering of any RB of the second CORESET is greater than or equal to the numbering of any RB of the first CORESET.

Step 303, the gNB informs the UE of the frequency location of the first resource and the frequency offset.

In an alternative mode, the terminal device may receive indication information from the network device, where the indication information is used to indicate a frequency offset; the indication information is one or more of the following signaling: SIB1, DCI scheduling SIB1, and MIB.

Herein, the PDCCH of the scheduling SIB1 is transmitted on CORESET #0. For example, when a red beacon UE initially accesses, it first searches for a cell-defining SSB (CD-SSB) of a defined cell, then determines CORESET #0 according to a MIB carried by a Physical Broadcast Channel (PBCH) included in the SSB, and the UE monitors a PDCCH for scheduling SIB1 on CORESET #0, and the SIB1 carries the indication information. Assuming that the network device configures a dedicated initial downlink BWP for the red beacon UE, SIB1 carries configuration information of the initial downlink BWP of the red beacon UE, and the first resource is the initial downlink BWP of the red beacon UE, the UE may determine the first resource and the frequency offset after acquiring SIB1, and then may determine a second CORESET according to the first resource and the frequency offset, that is, the CORESET configured for the red beacon UE.

Wherein, the indication information can also be carried by the MIB. For example, MIB carried by PBCH includes configuration information of CORESET #0, where the configuration information is used to determine an index, and the index is used to determine a bandwidth and a number of OFDM symbols of CORESET #0, and in this application, the index may also be used to determine a frequency offset. The UE may determine the frequency offset after acquiring the MIB.

Wherein, the indication information can also be carried by the DCI and the DCI of the scheduling SIB1 together. For example, SIB1 is used to configure a plurality of frequency offsets, and the DCI scheduling said SIB1 is used to indicate from said plurality of frequency shifts a frequency offset, which the terminal device uses to determine the second CORESET frequency location, of which one is valid.

Optionally, the indication information may also be carried by other SIBs besides SIB1, for example, SIB2, or RRC signaling in RRC connected state, DCI, or media access control element (MAC CE).

In addition, the bandwidth of the second core set and/or the number of OFDM symbols of the second core set may also be indicated by the indication information. For example, the indication information determines an index, if the index is 1, the index 1 not only corresponds to a frequency offset, but also corresponds to a bandwidth of the second CORESET, and/or the number of OFDM symbols of the second CORESET, and according to the index, the terminal device may determine the frequency offset, the bandwidth of the second CORESET, and the number of OFDM symbols of the second CORESET. In addition, the bandwidth of the second core set and/or the number of OFDM symbols of the second core set may also be indicated by another index, for example, the index indicating the frequency offset is index 1, and the bandwidth of the second core set and/or the number of OFDM symbols of the second core set may be indicated by index a. The manner of indicating the bandwidth of the second core set and/or the number of OFDM symbols of the second core set is not specifically limited in this application.

It should be noted that, the protocol may predefine 1 or more frequency offsets, one of which may be indicated by the indication information, and is not specifically limited herein, for example, in the predefined table of CORESET #0, a column is added for indicating the frequency offset, as shown by the last column in table 1 and table 2, where each row in table 1 includes one frequency offset value, and each row in table 2 includes 4 frequency offset values. For example, index 1 in table 1 corresponds to Value1 of the frequency offset.

Table 1: RB number and OFDM symbol number set of CORESET #0, sub-carriers corresponding to SSB and PDCCH are both 15KHz, frequency band with minimum channel bandwidth of 5MHz or 10MHz is corresponding, and each row corresponds to frequency domain offset of 1 second CORESET relative to the first resource

Table 2: RB number and OFDM symbol number set of CORESET #0, subcarrier corresponding to SSB and PDCCH is 15KHz, frequency band with minimum channel bandwidth of 5MHz or 10MHz is corresponding to each row, and frequency domain deviation value of 4 second CORESET corresponding to first resource is corresponding to each row

In table 1, the frequency offset values of the second CORESET corresponding to two rows of the table may be the same or different with respect to the first resource, which is not limited herein. The frequency offset values of the 4 second CORESET corresponding to two rows in table 2 with respect to the first resource may all be the same, or all be different, or only be partially the same, which is not limited herein.

It should be understood that table 1 and table 2 are specific examples of carrying the indication information through the MIB, that is, the index for determining the CORESET #0 parameter is also used for determining the frequency offset, but in practical applications, the indication information may also be carried in other forms and through other information, and the application is not limited in this application.

Note that the frequency offset may be a number equal to or greater than 0, or may be greater than 0, less than 0, or equal to 0. For example, the frequency offset represents a frequency offset from the first RB of the red map initial downlink BWP to the first RB of the second CORESET, and in this case, the frequency offset is a number equal to or greater than 0, and if the frequency offset is greater than 0, the first RB of the second CORESET is located at a position in a direction from the first RB of the red map initial downlink BWP to the increasing RB number, and if the frequency offset is equal to 0, the first RB of the second CORESET is aligned with the first RB of the red map initial downlink BWP, and the alignment may be understood as a frequency offset of 0 or a fixed value. The frequency offset may also represent a frequency offset from the center frequency of the red map initial downlink BWP to the center frequency of the second core set, and if the frequency offset is greater than 0, it represents that the center frequency of the second core set is located at a position in a direction from the center frequency of the red map initial downlink BWP toward the RB number increasing direction; if the frequency offset is less than 0, it indicates that the center frequency of the second CORESET is located at a position in a direction decreasing from the center frequency of the red map initial downlink BWP to the RB number; if the frequency offset is equal to 0, it indicates that the center frequency of the second CORESET is aligned with the center frequency of the RedCap downstream BWP.

In addition, the start position and the end position of the frequency offset can be determined according to the sign of the frequency offset, and then the position of the second CORESET can be determined. For example, if the frequency offset is equal to 0, the first RB representing the second CORESET is aligned with the first RB of the red map initial downlink BWP; if the frequency offset is greater than 0, the starting position of the frequency offset is the first RB of the RedCap initial downlink BWP, the ending position of the frequency offset is the first RB of the second CORESET, the frequency offset represents the frequency offset from the first RB of the RedCap initial downlink BWP to the first RB of the second CORESET, and the first RB of the second CORESET is positioned in the direction of increasing RB numbers from the first RB of the RedCap initial downlink BWP; if the frequency offset is less than 0, the starting position of the frequency offset is the last RB of the RedCap initial downlink BWP, the ending position of the frequency offset is the last RB of the second CORESET, the absolute value of the frequency offset indicates the frequency offset from the last RB of the RedCap initial downlink BWP to the last RB of the second CORESET, and the last RB of the second CORESET is located at a position in a direction of decreasing RB number from the last RB of the RedCap initial downlink BWP. In this way, the location of the second CORESET may be more flexibly configured.

As another example, if the frequency offset is equal to 0, the frequency offset indicates that the lower boundary of the first RB of the second CORESET is aligned with the upper boundary of the last RB of the first CORESET. If the frequency offset is greater than 0, the frequency offset represents a frequency offset from an upper boundary of a last RB of the first CORESET to a lower boundary of a first RB of the second CORESET, and the first RB of the second CORESET is located at a position in a direction of increasing RB numbers from the last RB of the first CORESET; if the frequency offset is less than 0, the absolute value of the frequency offset represents the frequency offset from the lower boundary of the first RB of the first CORESET to the upper boundary of the last RB of the second CORESET, and the last RB of the second CORESET is located at a position in a direction of decreasing RB number from the first RB of the first CORESET. Therefore, the absolute value of the frequency domain offset can be as small as possible, which is beneficial to indicating by using less bit numbers and saving signaling overhead. In this way, the second CORESET is configured not to overlap with the first CORESET, which is beneficial to expanding the system capacity and reducing PDCCH congestion.

In addition, if the RB of the first resource has the same subcarrier spacing as the RB of the second core set, the two RB alignments are equivalent to center frequency alignments of two RBs, center frequency alignments of first REs of two RBs, lower boundary alignments of two RBs, or the like. If the subcarrier spacing of the two RBs is different, the two RBs are aligned, which can be understood as one of the following: center frequency alignment of two RBs, lower boundary alignment of two RBs, center frequency alignment of first RE of two RBs.

Step 304, the UE determines the frequency location of the second CORESET according to the frequency location of the first resource and the frequency offset. It should be noted that, after performing step 304, the UE may send information (the sent message may be feedback information or response information for determining the frequency location of the second core set, for example, indicated by sending Physical Random Access Channel (PRACH) information or the like) to the gNB to notify the gNB, for example, the UE may send PRACH to the gNB, and then the gNB may learn that the UE has determined the frequency location of the second core set, and then step a may be performed.

Step A, the gNB sends the PDCCH in a second CORESET.

And 305, the UE monitors the PDCCH in a second CORESET.

As an example, the UE may determine, with reference to fig. 4A, that the UE determines the first resource during the initial access, and then, according to the frequency offset, the UE may determine the frequency location of core set # R. The time interval between the first resource and the core set # R is only for illustration. The frequency location of the second CORESET may also be determined by the execution flow of the resource determination method illustrated in fig. 4B:

step 401, searching and receiving SSB, and analyzing the information carried by PBCH to obtain the configuration information of MIB.

Step 402, determining the frequency position of CORESET #0 according to the configuration information of the MIB.

Step 403, monitoring the PDCCH for scheduling SIB1 on CORESET #0, and further receiving the PDSCH carrying SIB1, and acquiring the configuration information of SIB1, where the configuration information of SIB1 includes information for determining the following resources and parameters: an initial downlink BWP of the recmap UE, an initial uplink BWP of the recmap UE, a frequency offset, an initial downlink BWP of the eMBB UE, and an initial uplink BWP of the eMBB UE.

Step 404, using the initial downlink BWP of the red beacon UE as the first resource, and determining the frequency location of the second CORESET according to the frequency offset, where the second CORESET is CORESET # R in fig. 4A.

Step 405, monitor PDCCH in the second CORESET, which can be used to schedule paging messages or schedule Msg2 or Msg4 in the random access procedure, or schedule system messages for the reccap UE.

The present application further provides another resource determining method, and in execution, refer to fig. 5, where fig. 5 illustrates a terminal device as a UE, but does not specifically limit a category of the terminal device in practical application, and illustrates the terminal device as a network device as a gNB by way of example:

step 501, the gNB determines the frequency position of a first resource and the frequency position of a second CORESET, wherein the first resource is BWP or the first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain. The first core set may be configured by system information, for example, MIB or SIB 1. The first CORESET may be a control resource set CORESET #0 identified as 0 configured by the network device for the terminal device, or may be other identified control resource sets, which is not specifically limited herein.

Step 502, the gNB informs the UE of the frequency location of the first resource.

In step 503, the ue determines the frequency location of the second CORESET according to the frequency location of the first resource.

Step A, the gNB sends the PDCCH in a second CORESET.

In step 504, the UE monitors the PDCCH in the second CORESET.

It should be noted that, in this scheme, the network device and the terminal device may agree in advance on the relative relationship between the frequency location of the first resource and the frequency location of the second CORESET, so that the terminal device may determine the frequency location of the second CORESET directly according to the frequency location of the first resource, which is more convenient and faster.

In an alternative approach, the first RB of the second CORESET is aligned with the first RB of the first resource; or, the last RB of the second CORESET is aligned with the last RB of the first resource; or, the center RB of the second CORESET is aligned with the center RB of the first resource; or, the lower boundary of the second CORESET is aligned with the lower boundary of the first resource; or, the upper boundary of the second CORESET is aligned with the upper boundary of the first resource; or, a center frequency of a first resource element, RE, of a first RB of a second CORESET is aligned with a center frequency of a first RE of the first RB of the first resource; or, the center frequency of the last resource element RE of the last RB of the second CORESET is aligned with the center frequency of the last RE of the last RB of the first resource; or, the upper boundary of the second CORESET is aligned with the preset frequency of the first resource; or, the lower boundary of the second CORESET is aligned with the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

The foregoing alignment may be understood as a frequency offset of 0 or a fixed value, for example, the alignment of the first resource block RB of the second core set with the first RB of the first resource may be understood as that there is no frequency offset between the first resource block RB of the second core set and the first RB of the first resource, or the frequency offset between the first resource block RB of the second core set and the first RB of the first resource is a fixed value.

In addition, the network device may further indicate candidate frequencies to the terminal device, where the first resource is aligned with the candidate frequencies of the second core set, such as the candidate frequencies are the first RB, the last RB, and the center RB. An indication of the network device may be received and one of the candidate RBs may be selected to determine the frequency location of the second CORESET.

For example, if the network device indicates that the candidate frequency is the first RB, then the first RB of the second CORESET is aligned with the first RB of the first resource. If the network device indicates that the candidate frequency is an upper boundary, it indicates that the upper boundary of the second CORESET and the upper boundary of the first resource are aligned.

In order to save resources of the processor, signaling overhead, and further save resource overhead and improve resource utilization efficiency, the second CORESET may be the same as the CORESET #0 configured by the MIB except for the frequency location, and the configuration except for the frequency location includes at least one of the following:

The bandwidth indicates the number of frequency domain RBs included in the control resource set; the number of OFDM symbols represents the number of time domain OFDM symbols included in the control resource set; the CCE-REG-MappingType indicates a mapping type from CCE to REG, for example, the mapping type includes interleaving (interleaved) mapping and non-interleaving (non-interleaved) mapping, and in addition, the configuration other than the frequency position further includes a specific mapping manner, for example, which REG chunks(s) one CCE specifically corresponds to; REG-bundle size represents the number of REGs included in one REG bundle; interleaver size, which represents the number of interleaver rows; precoding indicates the resource size using the same precoding, for example, precoding is set to sameAsREG-bundle indicates that the data uses the same precoding in one REG bundle, and precoding is set to allContiguoussRBs indicates that the data uses the same precoding in all REGs in CORESET; and the PDCCH-DMRS-ScramblingID represents a number used for PDCCH DMRS scrambling code initialization.

Further, the configuration of the second CORESET associated search space set may be the same as the configuration of the CORESET #0 associated search space set, the configuration of the search space set comprising at least one of:

monitoring period, period offset, number of continuous monitoring time slots of each monitoring occasion, monitoring symbols in the monitoring occasions, candidate PDCCH aggregation level, PDCCH candidate number corresponding to the candidate PDCCH aggregation level, search space set type (common or special), and DCI format related to the search space set.

The monitoring period is used for determining the monitoring period of the search space set, and the period offset is used for determining the start of each monitoring period, namely the start time slot of the PDCCH monitoring opportunity in each monitoring period; the number of the continuous time slots of each monitoring opportunity represents the number of the continuous time slots including the PDCCH monitoring opportunity in each monitoring period; the monitoring symbol in the monitoring opportunity represents the initial symbol of the PDCCH monitoring opportunity in the time slot; the candidate PDCCH aggregation level represents the number of CCEs included in the candidate PDCCH; the search space set type (public or private) indicates whether the search space set is used for a group of terminal devices or only for one UE; the DCI formats associated with a search space set indicate possible DCI formats for the PDCCH bearer transmitted in the search space set.

It should be understood that one core set is associated with one search space set, which means that the UE monitors the PDCCH in the core set according to the parameters determined by the associated search space set.

It should be understood that core set #0 may be associated with 1 or more search space sets, and accordingly, the search space sets associated with the second core set are also 1 or more, respectively, and the configuration of each search space set is the same as that of the corresponding search space set associated with core set #0. For example, if CORESET #0 is associated with the type 0-PDCCH common search space set, the type 0A-PDCCH common search space set, the type 1-PDCCH common search space set, and the type 2-PDCCH common search space set, then the second CORESET is also associated with the type 0-PDCCH common search space set, the type 0A-PDCCH common search space set, the type 1-PDCCH common search space set, and the type 2-PDCCH common search space set. Wherein the type 0-PDCCH common search space set is used for monitoring a DCI format of which Cyclic Redundancy Check (CRC) is scrambled by a system information-radio network temporary identity (SI-RNTI), and the DCI format is used for scheduling SIB1 signaling. The type 0A-PDCCH common search space set is used to monitor DCI formats whose CRC is scrambled by SI-RNTI, which are used to schedule other system messages, i.e., other SIBs than SIB1, e.g., SIB2-SIBx. The type 1-PDCCH common search space set is used for monitoring a DCI format of which CRC is scrambled by a random access radio network temporary identifier (RA-RNTI), a Message B radio network temporary identifier (Message B-RNTI, msgB-RNTI) or a temporary cell radio network temporary identifier (TC-RNTI). The type 2-PDCCH common search space set is used to monitor a DCI format whose CRC is scrambled by a paging-radio network temporary identity (P-RNTI).

Optionally, if the second core set and the core set #0 are both associated with a paging search space set, that is, a type 2-PDCCH common search space set, the configuration used by the terminal device when the second core set monitors the paging PDCCH is the same as the configuration used when the core set #0 monitors the paging PDCCH, where the configuration used when monitoring the paging PDCCH includes at least one of the following configurations: a default paging cycle, a ratio of paging frames to paging cycles (for calculating the number of paging frames in one paging cycle), a paging frame offset, the number of paging occasions in a paging frame, and a first PDCCH monitoring occasion time domain position of each Paging Occasion (PO) in a paging frame. Wherein the default paging cycle represents a paging cycle of system message broadcasting; the paging frame represents a radio frame including 1 or more paging occasions; the paging frame offset is used for the terminal equipment to determine a System Frame Number (SFN) of the paging frame; one PO is a set including one or more PDCCH monitoring occasions (PDCCH monitoring occasions), and the number of PDCCH monitoring occasions included in one PO is equal to the number of SSBs actually transmitted in one SSB period, that is, the number of SSBs actually transmitted included in one synchronization signal cluster (SS burst set).

In one example, the second core set is a core set configured for the red beacon UE during initial access, the core set #0 configured by the MIB is within a frequency domain range, the network device further configures a common core set, for example, numbered 1, i.e., common core set #1, for the eMBB UE through SIB1, then the bandwidth of the second core set is the same as the bandwidth of core set #0, and the frequency domain range of the second core set also includes a common core set without limiting the number thereof, for example, called common core set # R1, and in the frequency domain, the relative position of the common core set # R1 within the second core set is the same as the relative position of the common core set #1 within core set #0, and the bandwidth of the common core set # R1 is the same as the bandwidth of the common core set #1, and the configuration of the search space set associated with the common core set # R1 is the same as the configuration of the search space set associated with the common core set # 1. Thus, the network device does not need to reconfigure a common control resource set in the second CORESET, and only needs to adopt the configuration same as that of the common CORESET #1, so that the signaling overhead can be saved.

It should be noted that, in the present application, the first resource may also be a first CORESET, and when the first resource is a BWP, the second CORESET may be the same as the CORESET #0 configured by the MIB except for the frequency position, and the configuration of the search space set associated with the second CORESET may also be the same as the configuration of the search space set associated with the CORESET #0. When the first resource is the first core set, the second core set may have the same configuration as the first core set except for the frequency position, the configuration of the search space set associated with the second core set may also have the same configuration as the search space set associated with the first core set, and the first core set may be core set #0 or other core sets, and is not particularly limited. Here, the configurations other than the frequency positions and the configurations of the search space sets may refer to the above description, and are not repeated herein.

Fig. 6 shows a communication apparatus, which may be understood as a terminal device, which may be UE, a vehicle-mounted device, a smart watch, a smart bracelet, etc., and may also be understood as a network device, which may be TRP, gNB, etc. The communication device may include: a processing unit 601 and an input-output unit 602. It should be understood that the input-output unit may be referred to as a transceiver unit, a communication unit, etc., and when the communication apparatus is a terminal device, the input-output unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in a terminal device, the input/output unit may be an input/output interface, an input/output circuit, an input/output pin, or the like, and may also be referred to as an interface, a communication interface, an interface circuit, or the like; the processing unit may be a processor, a processing circuit, a logic circuit, or the like. The communication device may be configured to perform the steps of the method embodiments corresponding to fig. 3 or fig. 5, and for the specific description of the implementation details, reference may be made to the method embodiment portion, which is not described herein again.

When the communication apparatus is a terminal device, the processing unit 601 is configured to determine a frequency offset and a frequency location of a first resource, where the first resource is a bandwidth portion BWP or a first control resource set CORESET; the frequency offset represents the frequency offset of the second CORESET relative to the first resource, and when the first resource is the first CORESET, the first CORESET and the second CORESET do not overlap in the frequency domain; determining the frequency position of a second CORESET according to the frequency position and the frequency offset of the first resource; an input/output unit 602, configured to monitor a physical downlink control channel PDCCH in the second CORESET.

When the communication apparatus is a network device, the processing unit 601 is configured to determine a frequency position of a first resource and a frequency position of a second control resource set, where the first resource is a bandwidth portion BWP or a first control resource set; when the first resource is a first CORESET, the first CORESET and the second CORESET are not overlapped in the frequency domain; determining a frequency offset according to the frequency position of the first resource and the frequency position of the second CORESET; the frequency offset represents a frequency offset of the second CORESET relative to the first resource; an input/output unit 602 configured to notify a terminal device of a frequency location and a frequency offset of the first resource; and sending a physical downlink control channel PDCCH at a second CORESET.

In an alternative approach, the frequency offset may represent: an offset of a first resource block RB of the second CORESET from a first RB of the first resource; or, the offset of the last RB of the second CORESET from the last RB of the first resource; or, the offset of the center RB of the second CORESET from the center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, an offset of a center frequency of a first resource element, RE, of a first RB of a second CORESET from a center frequency of a first RE of a first RB of a first resource; or, an offset of a center frequency of a first resource element RE of a last RB of a second CORESET from a center frequency of a first RE of a last RB of a first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the deviation of the lower boundary of the second CORESET from the preset frequency of the first resource; the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

It should be noted that, in practical applications, the frequency offset specifically indicates which frequency amount of the first resource is offset from which frequency amount of the second core set, which may be determined according to service requirements, and is not specifically limited herein.

In an optional manner, the input/output unit 602 of the terminal device is further configured to: receiving indication information, wherein the indication information is used for indicating frequency offset; the indication information is one or more of the following signaling:

SIB1, DCI scheduling SIB1, and MIB.

By adopting the signaling, the terminal equipment can acquire the frequency offset after acquiring the DCI/MIB of the SIB 1/scheduling SIB1 in the initial access stage, and the determination of the frequency position of the second CORESET in the initial access stage is facilitated, so that the load balance can be realized in the initial access stage, and the congestion of the PDCCH is reduced.

In an optional manner, the indication information is further used for indicating a bandwidth of the second core set, and/or a number of OFDM symbols of the second core set. For example, the indication information determines an index, if the index is 1, the index 1 not only corresponds to a frequency offset, but also corresponds to a bandwidth of the second CORESET, and/or the number of OFDM symbols of the second CORESET, and according to the index, the terminal device may determine the frequency offset, the bandwidth of the second CORESET, and the number of OFDM symbols of the second CORESET. In addition, the bandwidth of the second core set and/or the number of OFDM symbols of the second core set may also be indicated by another index, for example, the index indicating the frequency offset is index 1, and the bandwidth of the second core set and/or the number of OFDM symbols of the second core set may be indicated by index a. The manner of indicating the bandwidth of the second CORESET and/or the number of OFDM symbols of the second CORESET is not specifically limited in this application.

By the method, the bandwidth of the second CORESET and the number of OFDM symbols of the second CORESET can be determined more flexibly. In addition, optionally, the indication information may be used to determine the bandwidth, the number of symbols, and the frequency offset of the second core set at the same time, so that signaling overhead may be saved, and it is not necessary to indicate the bandwidth, the number of symbols, and the frequency offset of the second core set separately.

By the method, the parameter of the second CORESET can be multiplexed with the parameter of the CORESET #0, the parameter of the second CORESET does not need to be configured separately, and the signaling overhead can be saved, especially when the second CORESET is configured in the initial access stage, the signaling overhead in the initial access stage can be saved, for example, the signaling overhead of the SIB1 can be saved.

In an alternative manner, the configuration of the second CORESET-associated search space set is the same as the configuration of the CORESET # 0-associated search space set, and the configuration of the search space set includes at least one of the following:

monitoring period, period offset, the number of continuous time slots of each monitoring occasion, monitoring symbols in the monitoring occasions, candidate PDCCH aggregation level, the number of PDCCH candidates corresponding to the candidate PDCCH aggregation level, search space set type (common or dedicated), and search space associated DCI format.

By this way, the parameters of the search space set associated with the second CORESET may multiplex the parameters of the search space set associated with the CORESET #0, and the parameters of the search space set associated with the second CORESET do not need to be configured separately, which may save signaling overhead, and especially when the second CORESET is configured in the initial access phase, may save signaling overhead in the initial access phase, for example, save signaling overhead of SIB 1.

In addition, as shown in fig. 7, a communication apparatus 700 is provided. Illustratively, the communication device 700 may be a chip or a system of chips. Optionally, the chip system in the embodiment of the present application may be formed by a chip, and may also include a chip and other discrete devices.

The communication device 700 may include at least one processor 710 and the communication device 700 may also include at least one memory 720 for storing computer programs, program instructions, and/or data. A memory 720 is coupled to the processor 710. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 710 may operate in conjunction with the memory 720. Processor 710 may execute computer programs stored in memory 720. Optionally, the at least one memory 720 may also be integrated with the processor 710.

Optionally, in practical applications, the transceiver 730 may be included in the communication apparatus 700 or not included in the communication apparatus 700, which is illustrated by a dashed box, and the communication apparatus 700 may perform information interaction with other devices through the transceiver 730. The transceiver 730 may be a circuit, a bus, a transceiver, or any other device that may be used to exchange information.

In a possible implementation manner, the communication apparatus 700 may be applied to the foregoing terminal device, and may also be the foregoing terminal device. The memory 720 holds the necessary computer programs, program instructions and/or data to implement the functionality of the terminal device in any of the embodiments described above. The processor 710 can execute the computer program stored in the memory 720 to perform the method of any of the above embodiments.

The specific connection medium among the transceiver 730, the processor 710 and the memory 720 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 720, the processor 710, and the transceiver 730 are connected by a bus in fig. 7, the bus is represented by a thick line in fig. 7, and the connection manner between other components is merely illustrative and not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but that does not indicate only one bus or one type of bus. In the embodiments of the present application, the processor may be a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory, for example, a random-access memory (RAM). The memory can also be, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing computer programs, program instructions, and/or data.

Based on the above embodiments, referring to fig. 8, the present embodiment further provides another communication apparatus 800, including: interface circuitry 810 and logic circuitry 820; the interface circuit 810, which may be understood as an input/output interface, may be configured to perform the same operation steps as the input/output unit illustrated in fig. 6 or the transceiver illustrated in fig. 7, and is not described herein again. The logic circuit 820 may be configured to execute the code instructions to perform the method in any embodiment described above, and it may be understood that the processing unit in fig. 6 or the processor in fig. 7 may implement the same functions as the processing unit or the processor, which is not described herein again.

Based on the foregoing embodiments, an embodiment of the present application further provides a readable storage medium, where the readable storage medium stores instructions that, when executed, cause the method performed by the security detection method in any of the foregoing embodiments to be implemented. The readable storage medium may include: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A method for resource determination, comprising:

determining a frequency offset and a frequency position of a first resource, wherein the first resource is a bandwidth part BWP or a first control resource set CORESET; the frequency offset represents a frequency offset of a second CORESET relative to the first resource, the first CORESET and the second CORESET do not overlap in a frequency domain;

determining the frequency position of the second CORESET according to the frequency position of the first resource and the frequency offset;

and monitoring a Physical Downlink Control Channel (PDCCH) in the second CORESET.

2. The method of claim 1, wherein the frequency offset represents:

an offset of a first resource block, RB, of the second CORESET from a first RB of the first resource; or the like, or, alternatively,

an offset of a last RB of the second CORESET relative to a last RB of the first resource; or, an offset of a center RB of the second CORESET from a center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, the center frequency of a first resource element, RE, of a first RB of the second CORESET is offset from the center frequency of a first RE of the first RB of the first resource; or, an offset of a center frequency of a first resource element, RE, of a last RB of the second CORESET from a center frequency of a first RE of a last RB of the first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the lower boundary of the second CORESET is offset from the preset frequency of the first resource;

the offset between the preset frequency of the first resource and the center frequency of the first resource is a preset value; the preset value is greater than 0.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

receiving indication information, wherein the indication information is used for indicating the frequency offset; the indication information is one or more of the following signaling:

system message block 1SIB1, downlink control information DCI for scheduling SIB1, and master information block MIB.

4. The method of claim 3, wherein the indication information is further used for indicating a bandwidth of the second CORESET and a number of OFDM symbols of the second CORESET.

5. The method according to any of claims 1-4, wherein the second CORESET is configured identically to CORESET #0 except for frequency location, wherein CORESET #0 is configured by system information, and wherein the configuration except for frequency location comprises at least one of:

bandwidth, the number of OFDM symbols, control channel elements and a resource element group mapping type cci-REG-MappingType, a resource element group size REG-BundleSize, an interleaver size, a precoding granularity, and a demodulation reference signal scrambling identifier (PDCCH-DMRS-ScramblingID) of a PDCCH.

6. The method according to any of claims 1-5, wherein the configuration of the second CORESET-associated search space set is the same as the configuration of the CORESET # 0-associated search space set, wherein the CORESET #0 is configured by system information, and wherein the configuration of the search space set comprises at least one of:

7. A method for resource determination, comprising:

determining the frequency position of a first resource and the frequency position of a second control resource set CORESET, wherein the first resource is a bandwidth part BWP or a first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain;

determining a frequency offset according to the frequency position of the first resource and the frequency position of the second CORESET; the frequency offset represents a frequency offset of a second CORESET relative to the first resource;

notifying a terminal device of the frequency location of the first resource and the frequency offset;

and sending a Physical Downlink Control Channel (PDCCH) at the second CORESET.

8. The method of claim 7, wherein the frequency offset represents:

an offset of a first resource block, RB, of the second CORESET from a first RB of the first resource; or the like, or a combination thereof,

an offset of a last RB of the second CORESET relative to a last RB of the first resource; or, an offset of a center RB of the second CORESET from a center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, an offset of a center frequency of a first resource element, RE, of a first RB of the second CORESET from a center frequency of a first RE of a first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the upper boundary of the second CORESET is offset from the preset frequency of the first resource; or, the offset of the lower boundary of the second CORESET relative to the preset frequency of the first resource;

9. The method according to claim 7 or 8, wherein the frequency offset is indicated by one or more of the following signalling:

10. The method of claim 9, wherein the signaling is further used to indicate a bandwidth of the second CORESET, a number of OFDM symbols of the second CORESET.

11. The method according to any of claims 7-10, wherein the second CORESET is configured identically to CORESET #0 except for frequency location, where CORESET #0 is configured by system information, where the configuration except for frequency location comprises at least one of:

12. The method according to any of claims 7-11, wherein the configuration of the second CORESET associated search space set is the same as the configuration of the CORESET #0 associated search space set, wherein the CORESET #0 is configured by system information, and wherein the configuration of the search space set comprises at least one of:

13. A communications apparatus, comprising:

a processing unit, configured to determine a frequency offset and a frequency location of a first resource, where the first resource is a bandwidth portion BWP or a first control resource set CORESET; the frequency offset represents a frequency offset of a second CORESET relative to the first resource, the first CORESET and the second CORESET do not overlap in a frequency domain; determining the frequency position of the second CORESET according to the frequency position of the first resource and the frequency offset;

and the input and output unit is used for monitoring a physical downlink control channel PDCCH in the second CORESET.

14. The apparatus of claim 13, wherein the frequency offset represents:

an offset of a last RB of the second CORESET relative to a last RB of the first resource; or, an offset of a center RB of the second CORESET from a center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, the center frequency of a first resource element, RE, of a first RB of the second CORESET is offset from the center frequency of a first RE of the first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the offset of the upper boundary of the second CORESET with respect to the preset frequency of the first resource; or, the offset of the lower boundary of the second CORESET relative to the preset frequency of the first resource;

15. The apparatus of claim 13 or 14, wherein the input-output unit is further configured to:

16. The apparatus of claim 15, wherein the indication information is further used for indicating a bandwidth of the second CORESET and a number of OFDM symbols of the second CORESET.

17. The apparatus according to any of claims 13-16, wherein the second CORESET is identical to CORESET #0 except for frequency location, said CORESET #0 being configured by system information, said configuration except for frequency location comprising at least one of:

18. The apparatus according to any of claims 13-17, wherein the second CORESET associated search space set has a same configuration as a CORESET #0 associated search space set, said CORESET #0 configured by system information, said configuration of search space set comprising at least one of:

19. A communications apparatus, comprising:

the processing unit is used for determining the frequency position of a first resource and the frequency position of a second control resource set CORESET, wherein the first resource is a bandwidth part BWP or a first CORESET; the first CORESET and the second CORESET do not overlap in a frequency domain; determining a frequency offset according to the frequency position of the first resource and the frequency position of the second CORESET; the frequency offset represents a frequency offset of a second CORESET relative to the first resource;

an input/output unit configured to notify a terminal device of the frequency location of the first resource and the frequency offset; and sending a physical downlink control channel PDCCH at the second CORESET.

20. The apparatus of claim 19, wherein the frequency offset represents:

an offset of a last RB of the second CORESET relative to a last RB of the first resource; or, an offset of a center RB of the second CORESET from a center RB of the first resource; or, the offset of the lower boundary of the second CORESET relative to the lower boundary of the first resource; or, an offset of an upper boundary of the second CORESET from an upper boundary of the first resource; or, the center frequency of a first resource element, RE, of a first RB of the second CORESET is offset from the center frequency of a first RE of the first RB of the first resource; or, the center frequency of the first resource element RE of the last RB of the second CORESET is offset from the center frequency of the first RE of the last RB of the first resource; or, the upper boundary of the second CORESET is offset from the preset frequency of the first resource; or, the offset of the lower boundary of the second CORESET relative to the preset frequency of the first resource;

21. The apparatus according to claim 19 or 20, wherein the frequency offset is indicated by one or more of the following signalling:

22. The apparatus of claim 21, wherein the signaling is further configured to indicate a bandwidth of the second CORESET, a number of OFDM symbols of the second CORESET.

23. The apparatus according to any of claims 19-22, wherein the second CORESET is identical to CORESET #0 except for frequency location, wherein CORESET #0 is configured by system information, and wherein the configuration except for frequency location comprises at least one of:

24. The apparatus of any of claims 19-23, wherein the configuration of the second CORESET associated search space set is the same as the configuration of the CORESET #0 associated search space set, wherein the CORESET #0 is configured by system information, wherein the configuration of the search space set comprises at least one of:

25. A communications apparatus, comprising: at least one processor and memory;

the memory for storing a computer program or instructions;

the at least one processor configured to execute the computer program or instructions to cause the method of any of claims 1-6 or any of claims 7-12 to be performed.

26. A computer-readable storage medium, characterized in that it stores instructions that, when executed by a computer, cause the method of any of claims 1-6 or any of claims 7-12 to be performed.

27. A computer program product comprising a computer program or instructions for causing the method of any one of claims 1 to 6 or 7 to 12 to be performed when the computer program or instructions is run on a computer.