Control channel transmission method and apparatus, device, and storage medium

Abstract

The present application relates to the technical field of communications, and discloses a control channel transmission method and apparatus, a device, and a storage medium. The control channel transmission method in embodiments of the present application comprises: a terminal acquiring configuration information of M frequency domain units, wherein M is less than or equal to the number P of frequency domain units configured by a serving cell of the terminal; acquiring frequency domain resources of CORESETs on the M frequency domain units; and on the basis of the configuration information of the M frequency domain units and the frequency domain resources of the CORESETs, determining at least one CORESET for receiving a PDCCH.

Description

Control channel transmission method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 8, 2023, with application number 202311691178.0 and invention name “Transmission method, device, equipment and storage medium for control channel”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of wireless communication technology, and specifically relates to a control channel transmission method, apparatus, device and storage medium. Background Art

[0004] The spectrum resources of new radio (NR) systems include the sub-6 GHz band. The sub-3 GHz band, which falls below 3 GHz, is called the sub-3 GHz band, and the remaining bands are called the C-band. The sub-3 GHz band is allocated to mobile operators in a fragmented manner, resulting in a relatively fragmented and discontinuous spectrum resource. Efficiently and flexibly utilizing these fragmented, narrow-bandwidth spectrum resources to provide users with high-capacity and high-bandwidth services is one of the challenges facing NR systems. Summary of the Invention

[0005] The embodiments of the present application provide a control channel transmission method, apparatus, device, and storage medium, which can provide users with high-capacity and high-bandwidth services by utilizing scattered, narrow-bandwidth spectrum resources.

[0006] In a first aspect, a control channel transmission method is provided, which is executed by a terminal, the method comprising: the terminal obtaining configuration information of M frequency domain units, M being less than or equal to the number P of frequency domain units configured in the service cell of the terminal; the terminal obtaining frequency domain resources of a control resource set CORESET on the M frequency domain units; the terminal determining at least one CORESET for receiving a physical downlink control channel PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0007] In a second aspect, a control channel transmission method is provided, which is executed by a network side device, the method comprising: the network side device sends configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a service cell of the terminal; the network side device sends the frequency domain resources of the CORESET on the M frequency domain units to the terminal; the network side device sends a downlink control channel PDCCH on at least one CORESET based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0008] In a third aspect, a control channel transmission device is provided, including: an acquisition module for acquiring configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal; the acquisition module is also used to acquire the frequency domain resources of the CORESET on the M frequency domain units; a determination module is used to determine at least one CORESET for receiving the PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0009] In a fourth aspect, a control channel transmission device is provided, including: a sending module for sending configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal; the sending module for sending the frequency domain resources of the CORESET on the M frequency domain units to the terminal; and a processing module for sending PDCCH on at least one CORESET based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0010] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0011] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to obtain configuration information of M frequency domain units, M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal, and obtain the frequency domain resources of the CORESET on the M frequency domain units; according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, at least one CORESET for receiving the physical downlink control channel PDCCH is determined, and the communication interface is used to receive the PDCCH on the at least one CORESET.

[0012] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0013] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to determine at least one CORESET for sending PDCCH based on the configuration information of M frequency domain units and the frequency domain resources of CORESET, M is less than or equal to the number P of frequency domain units configured by the service cell of the terminal, and the communication interface is used to send the configuration information of M frequency domain units to the terminal, send the frequency domain resources of the CORESET on the M frequency domain units to the terminal, and send PDCCH to the terminal through the at least one CORESET.

[0014] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0015] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0016] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0017] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the control channel transmission method as described in the first aspect or the second aspect.

[0018] In an embodiment of the present application, the network side device can reduce the common signaling overhead and achieve load balancing of each uplink UL / DL carrier by configuring CORESET on part of the frequency domain units of the terminal's service cell. The terminal combines all or part of the CORESET cross-frequency domain units on M frequency domain units to obtain a CORESET for receiving PDCCH, so that the CORESET for receiving PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 shows a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0020] FIG2 is a flow chart of a control channel transmission method provided in Example 1 of the present application;

[0021] FIG3 is a schematic diagram showing the position of the starting RB of a BWP relative to the frequency domain starting point of the carrier where the BWP is located;

[0022] FIG4 is a schematic diagram of frequency reference points of each frequency domain unit of a terminal;

[0023] FIG5 is a schematic diagram of configuring CORESET for all frequency domain units of a serving cell of a terminal;

[0024] FIG6 is a schematic diagram of configuring CORESET of some frequency domain units of a serving cell of a terminal;

[0025] FIG7 is a flowchart of a control channel transmission method provided in Example 2 of the present application;

[0026] FIG8 is a schematic diagram of a cascade connection of a CORESET of multiple frequency domain units;

[0027] FIG9 is another schematic diagram of a cascade of a CORESET of multiple frequency domain units;

[0028] FIG10 is another schematic diagram of a cascade of a CORESET of multiple frequency domain units;

[0029] FIG11 is a schematic diagram of a cascade of CORESET frequency domain units of multiple terminals;

[0030] FIG12 is a flowchart of a control channel transmission method provided in Example 3 of the present application;

[0031] FIG13 is a schematic diagram of a CORESET of a frequency domain unit of a terminal;

[0032] FIG14 is a flowchart of a control channel transmission method provided in Embodiment 4 of the present application;

[0033] FIG15 is a signaling flow chart of a control channel transmission method provided in Embodiment 5 of the present application;

[0034] FIG16 is a schematic structural diagram of a control channel transmission device provided in Example 6 of the present application;

[0035] FIG17 is a schematic structural diagram of a control channel transmission device provided in Example 7 of the present application;

[0036] FIG18 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0037] FIG19 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application;

[0038] Figure 20 is a schematic diagram of the hardware structure of a network-side device implementing an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0040] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0041] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0042] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes the NR system for illustrative purposes, and the NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6G) NR system. th Generation, 6G) communication system.

[0043] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (homeevolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0044] In order to better understand the embodiments of this application, the following contents are first introduced:

[0045] (1) Physical Downlink Control Channel (PDCCH)

[0046] PDCCH is a downlink control channel, which carries downlink control information (DCI) of the physical uplink shared channel (PUSCH) and the physical downlink shared channel (PDSCH). In the LTE system, PDCCH occupies the entire bandwidth in the frequency domain and the first 1-3 symbols of each subframe in the time domain. In the NR system, if PDCCH continues to occupy the entire bandwidth in the same way as LTE, it will cause a waste of resources and place high demands on the terminal. Therefore, the frequency domain resources of PDCCH in the NR system are located within the bandwidth part (BWP), and the time domain does not occupy fixed time slots. The PDCCH time and frequency resources in the NR system are mainly determined by the control resource set (CORESET) and the search space.

[0047] (2)BWP

[0048] BWP is a collection of multiple consecutive resource blocks (RBs) within a carrier. In the NR system, the network side can dynamically configure the system bandwidth of the terminal according to different service types, which can reduce terminal power consumption and save network resources.

[0049] For example, BWP's technical advantages are mainly in four aspects:

[0050] 1. The terminal does not need to support all bandwidths, but only needs to meet the minimum bandwidth requirements, which is conducive to the development of low-cost terminals.

[0051] 2. When the terminal business volume is not large, the terminal can switch to low bandwidth operation, which can significantly reduce power consumption.

[0052] 3.5G technology is forward compatible. When 5G adds new technologies, the new technologies can be directly run on the new BWP, ensuring the forward compatibility of the system.

[0053] 4. Adapt to business needs and dynamically configure BWP for the business.

[0054] Exemplarily, the network side can dynamically adjust the bandwidth of the terminal according to the size of the business volume. For example, at the first moment, the business volume of the terminal is large, and the network side configures a large bandwidth (BWP1) for the terminal; at the second moment, the business volume of the terminal is small, and the network side configures a small bandwidth (BWP2) for the terminal to meet basic communication needs; at the third moment, the network side finds that there is large-scale frequency selective fading in the bandwidth where BWP1 is located, or the resources in the frequency range where BWP1 is located are relatively scarce, so it configures a new bandwidth (BWP3) for the terminal.

[0055] The frequency points and widths of the multiple BWPs configured by the network for the terminal are different. Optionally, other configuration parameters of the multiple BWPs can also be different. For example, the subcarrier spacing (SCS), cyclic prefix (CP) type, synchronization broadcast block (SSB) period, etc. of each BWP can be configured differently. Among them, SSB includes synchronization signals and broadcast signals. The synchronization signal includes the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). The broadcast signal includes the physical broadcast channel (PBCH) data and the PBCH demodulation reference signal (DMRS) signal.

[0056] (3) CORESET

[0057] In the NR system, in order to improve resource utilization and reduce the complexity of terminal blind detection, the concept of CORESET is introduced so that PDCCH no longer occupies the entire bandwidth.

[0058] A CORESET is a set of physical resources used to carry PDCCH or DCI. CORESET-related parameters include:

[0059] A resource element (RE) consists of one subcarrier in the frequency domain and one orthogonal frequency-division multiplexing (OFDM) symbol in the time domain.

[0060] Resource Block (RB) consists of 12 REs.

[0061] A resource element group (RE group, REG) consists of one RB (12 REs) in the frequency domain and one OFDM symbol in the time domain.

[0062] Resource element group sets (REG Bundles) consist of multiple REGs, the number of which is determined by the Radio Resource Control (RRC) parameter reg-bundle-size. The bundle size can be {2, 3, 6}, which is related to the number of CORESET symbols.

[0063] A control channel element (CCE) consists of 6 REGs.

[0064] Aggregation Level (AL) indicates how many CCEs are allocated to the PDCCH. Currently supported aggregation levels are {1, 2, 4, 8, 16}.

[0065] CORESET describes the frequency domain characteristics of the PDCCH blind detection resources. The PDCCH blind detection resources also include time domain characteristics. The frequency domain characteristics of the PDCCH are described by the search space (SS), which is used to describe the starting symbol of the PDCCH, the detection period, etc.

[0066] A CORESET can be composed of multiple PRBs in the frequency domain and 1 / 2 / 3 OFDM symbols in the time domain. The number and position of PRBs occupied by the CORESET can be flexibly deployed by the network side. For example, the CORESET has the following features:

[0067] The PRBs occupied by a CORESET can be continuous or discontinuous;

[0068] A CORESET can occupy one or more consecutive symbols in the time domain. The number of symbols can be: {1, 2, 3};

[0069] When CORESET occupies one symbol in the time domain, the REG bundle size can be {2, 6};

[0070] When CORESET occupies 2 / 3 symbols in the time domain, the REG bundle size can be equal to the number of time domain symbols or 6;

[0071] A terminal can be configured with one or more CORESETs, with a maximum of 3 CORESETs per BWP per cell;

[0072] A CORESET can be associated with two search spaces: Common Search Space and UE-specific Search Space.

[0073] Each BWP can be configured with up to 3 CORESETs;

[0074] Each BWP can be configured with up to 10 search spaces;

[0075] Multiple CORESETs configured on a terminal can overlap in the frequency or time domain;

[0076] In each CORESET, the mapping mode of CCE to REG can be interleaved or non-interleaved, but a CORESET can only have one mapping mode.

[0077] Compared to LTE / LTE-A systems, NR systems pursue greater bandwidth and throughput. They utilize fragmented sub-3 GHz spectrum to provide users with high bandwidth and capacity to meet the growing demand for business-oriented (To Business) and consumer-oriented (To Customer) services. Cells that utilize these fragmented continuous or discontinuous spectrum are called flexible serving cells. The purpose of flexible serving cells is to efficiently and flexibly utilize these fragmented spectrums.

[0078] The following, in conjunction with the accompanying drawings, describes in detail the control channel transmission method provided by the embodiments of the present application through some embodiments and their application scenarios. The following embodiments can be combined with each other, and the same or similar concepts and processes may not be repeated in some embodiments.

[0079] Example 1

[0080] Figure 2 is a flow chart of a control channel transmission method provided in Example 1 of the present application, which is applied to a terminal. As shown in Figure 2, the method provided in this embodiment includes the following steps.

[0081] S101. A terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.

[0082] Optionally, the frequency domain unit may be a BWP, a carrier, or a frequency band. A frequency band may include multiple carriers, and a carrier may include multiple BWPs. It is understood that the configuration information of different types of frequency domain units may be different.

[0083] Exemplarily, the configuration information of the M frequency domain units includes at least one of the following:

[0084] Frequency reference points of M frequency domain units;

[0085] The frequency offset value (offsetToCarrier) of each frequency domain unit in the M frequency domain units relative to the frequency reference point;

[0086] The SCS of each frequency domain unit in the M frequency domain units;

[0087] The CP of each frequency domain unit in the M frequency domain units;

[0088] The starting RB and size of each frequency domain unit in the M frequency domain units;

[0089] The index (or identifier) ​​of each frequency domain unit in the M frequency domain units.

[0090] Part or all of the configuration information in the M frequency domain units may be configured by the network side device and sent to the terminal. For information not configured by the network side device, the terminal may determine it based on other information.

[0091] It should be noted that for the P frequency domain units configured in the serving cell, the configuration information of the above frequency domain units is required so that the terminal can receive data, such as PDSCH or PUSCH. Since this application emphasizes the processing of CORESET, the P frequency domain units are not described in detail.

[0092] In the NR system, the bandwidth of the terminal's frequency domain unit is not necessarily equal to the channel bandwidth. For example, the channel bandwidth is 100MHz, and the bandwidth of the BWP allocated to the terminal by the network side is 20MHz. If the terminal does not use the full bandwidth of the channel bandwidth, then the terminal needs to determine the starting frequency of the frequency domain unit allocated to it based on the frequency reference point.

[0093] In the NR system, the frequency reference point may be Point A, which is the common reference point of the entire resource grid. Optionally, the frequency reference points of the M frequency domain units include at least one of the following:

[0094] There is no frequency reference point of a frequency domain unit associated with a Cell-Defining Synchronization Signal Block (CD-SSB) among the M frequency domain units;

[0095] A common frequency reference point for the frequency domain units that are not associated with CD-SSB among the M frequency domain units;

[0096] A frequency reference point for each of the M frequency domain units;

[0097] A common frequency reference point for M frequency domain units.

[0098] In the embodiment of the present application, when the frequency domain unit is a BWP, even if the CD-SSB is not within an initial BWP, the CD-SSB may be associated with the BWP. A similar definition can be used when the frequency domain unit is a carrier / band. Optionally, a carrier / band without an associated CD-SSB can be defined as having no CD-SSB on that carrier / band.

[0099] Some of the M frequency domain units are associated with CD-SSB, while others are not associated with CD-SSB. For the frequency domain units associated with CD-SSB, the frequency reference point of the frequency domain unit can be determined based on some acquired parameters of the frequency domain unit; for the frequency domain units not associated with CD-SSB, the network side device can configure the frequency reference point for the frequency domain unit, wherein the frequency reference points of different frequency domain units can be different.

[0100] Taking the frequency domain unit as BWP and the system adopting time division duplexing (TDD) as an example, the network side device indicates or configures a frequency reference point (eg, point A) for at least one frequency domain unit in the following manner.

[0101] For a DL BWP associated with CD-SSB, its frequency reference point does not need to be configured by the network-side device. It can be determined based on the lowest frequency domain position of the SSB frequency, the subcarrier offset k_ssb parameter, and offsetToPoint A. For example, it is calculated using the following formula:

[0102] The frequency reference point of point A = the lowest frequency domain position of the SSB associated BWP - k_ssb*u - offsetToPoint A*12*u.

[0103] Among them, u is the subcarrier spacing, which is 15kHz for FR1 and 60kHz for FR2. The subcarrier offset k_ssb parameter and offsetToPoint A can be notified by the network side device in the Master Information Block (MIB) message.

[0104] For a DL BWP that is not associated with a CD-SSB, the network side device may configure a frequency domain reference point for each carrier. The network side device may configure the frequency domain reference point for each carrier through a System Information Block (SIB) message.

[0105] When the frequency domain unit is BWP, the network side device configures the position of the starting RB and the size of the BWP for each BWP, where the position of the starting RB refers to the starting RB relative to the frequency domain starting point of the carrier where the BWP is located. The carrier frequency domain starting point is provided by offsetToCarrier, which is an offset value relative to pointA. This parameter is notified in the SIB.

[0106] Refer to Figure 3, which is a schematic diagram of the position of the starting RB of the BWP relative to the frequency domain starting point of the carrier where the BWP is located. The figure includes three BWPs: BWP i, BWP j and BWP k. BWP i, BWP j and BWP k are respectively located on three different carriers: carrier p, carrier q and carrier m. The positions of Point A of the carriers where the three BWPs are located are different. The positions of the starting RBs of the three BWPs are and The size of 3 BWPs can be expressed as and The subscripts i, j, and k are used to distinguish different BWPs.

[0107] Optionally, the frequency reference point of the frequency domain unit associated with the CD-SSB can be obtained based on the SSB, and the frequency reference points of other frequency domain units can be configured to be the same. For example, Figure 4 is a schematic diagram of the frequency reference points of each frequency domain unit of the terminal. Referring to Figure 4, the frequency reference points of carrier q and carrier p are the same, carrier m is the carrier where the CD-SSB is located, and the frequency reference point of carrier m is different from the frequency reference points of carrier p and carrier q. Optionally, the frequency reference point of the carrier where the CD-SSB is located can also be the same as the frequency reference points of other carriers.

[0108] S102. The terminal obtains frequency domain resources of the CORESET on M frequency domain units.

[0109] The terminal's serving cell is configured with P frequency domain units. Unlike the prior art, which requires configuring a CORESET on each frequency domain unit, in this embodiment, the network-side device can configure a CORESET on all or part of the P frequency domain units. When M is equal to P, the network side configures a CORESET on all frequency domain units of the serving cell. When M is less than P, the network side configures a CORESET on some frequency domain units of the serving cell.

[0110] Figure 5 is a schematic diagram of configuring CORESETs for all frequency domain units of a terminal's serving cell, and Figure 6 is a schematic diagram of configuring CORESETs for some frequency domain units of a terminal's serving cell. Referring to Figures 5 and 6, the serving cell of the terminal is configured with three frequency domain units: frequency domain unit A, frequency domain unit B, and frequency domain unit C. The three frequency domain units can be BWPs, carriers, or frequency bands. In Figure 5, all three frequency domain units are configured with CORESETs, and in Figure 6, frequency domain units B and C are configured with CORESETs, while frequency domain unit A is not configured with a CORESET.

[0111] It can be understood that Figures 5 and 6 are only schematic diagrams and do not constitute a limitation. The bandwidth of each frequency domain unit can be the same or different, the number of CORESETs configured on each frequency domain unit can be the same or different, and multiple CORESETs in each frequency domain unit can overlap in the frequency domain or time domain.

[0112] By configuring CORESET on some frequency domain units of the terminal's serving cell, public signaling overhead can be reduced and load balancing of each uplink (UL) / downlink (DL) carrier can be achieved.

[0113] The frequency domain resources of a CORESET may be continuous or discontinuous. Each CORESET has a CORESET identity (ID), which uniquely identifies a CORESET among all BWPs in a serving cell.

[0114] The terminal can obtain the frequency domain resources of the CORESET on the frequency domain unit through the frequencyDomainResources parameter. For example, the frequency domain resources of the CORESET can be indicated by a 45-bit bitmap. Each bit can indicate an RB group (for example, 6 PRBs). The value of each bit is 0 or 1. 1 indicates that the RB group corresponding to the bit is the frequency domain resource of the CORESET, and 0 indicates that the RB group corresponding to the bit is not the frequency domain resource of the CORESET.

[0115] The RB group corresponding to the first bit (Most Significant Bit, MBS) of the frequencyDomainResources field is the first RB group on the corresponding frequency domain unit, rather than the first RB group on the corresponding CORESET.

[0116] When the frequency domain unit is BWP, the commonRB sequence number corresponding to the first RB of the first RB group on the BWP is: Among them, the value of m is 6, Indicates the location of the starting RB of BWPi. Optionally, any one of the M frequency domain units can be used to send downlink control information to improve flexibility. For example, in the frequency band units shown in Figures 5 and 6, the network-side device can only send downlink control information on the CORESET of frequency domain unit C.

[0117] The downlink control information includes system information and paging information, etc. The system information includes SSB, System Information Block (SIB), Remaining Minimum System Information (RMSI), and Other System Information (OSI). The downlink control information includes necessary information, such as the frequency of each carrier, SCS, Random Access Channel (RACH) resources, etc. Accordingly, the terminal can receive the PDCCH of MSG2 in the random access process on a subset of frequency domain units (one frequency domain unit).

[0118] S103: The terminal determines at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0119] The method of the embodiment of the present application can be used before or after the RRC connection is established. Before the RRC connection is established, the CORESET configuration information involved in this article can be notified through the SIB. After the RRC connection is established, the CORESET configuration information involved in this article can be notified through an RRC message.

[0120] One or more CORESETs can be configured on each frequency domain unit. Assuming that a total of N1 CORESETs are configured on M frequency domain units, the value of N1 is greater than or equal to M, that is, the M frequency domain units include at least M CORESETs. The terminal can combine all or part of the CORESETs on the M frequency domain units across the frequency domain units according to predefined rules or instructions from the network-side device to obtain a CORESET for receiving the PDCCH, so that the CORESET used to receive the PDCCH has a larger bandwidth.

[0121] A CORESET with a larger bandwidth can support a higher aggregation level. For example, aggregation level AL 16 requires 96 RBs (16 CCEs). A narrow bandwidth carrier is usually unable to carry CCEs with a higher aggregation level. The method of this embodiment enables the terminal to support a higher aggregation level by combining CORESETs on multiple frequency domain units across frequency domain units, thereby increasing the coverage capability of the PDCCH. A CORESET with a larger bandwidth can also reduce the probability of PDCCH collision and increase the reliability of PDCCH transmission.

[0122] In one implementation, the terminal determines the order of the CORESETs on the M frequency domain units, and cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET, which is used to receive the PDCCH.

[0123] In this way, the CORESETs on M frequency domain units can be cascaded across frequency domain units to form one or more cascaded CORESETs. Each cascaded CORESET includes one or more CORESETs. The bandwidth of the cascaded CORESET is usually larger than that of the non-cascaded CORESET, so that PDCCH can be received over a larger bandwidth. It is worth noting that if a frequency domain unit is configured with multiple CORESETs, the network can instruct the terminal to cascade a subset of the CORESETs, that is, the CORESETs on a frequency domain unit can partially participate in the cascade or partially not participate in the cascade, depending on the flexible configuration of the network.

[0124] In this implementation, the network does not need to consider the capabilities of the terminal, that is, the network does not need to consider the capabilities of the terminal when configuring M frequency domain units for the terminal device.

[0125] In this implementation, when M is less than P, that is, when a CORESET is configured on only M frequency domain units out of the P frequency domain units, the PDCCH carried or sent on the cascaded CORESET is used to schedule data for the P frequency domain units, or the control information in the PDCCH carried or sent on the cascaded CORESET is used to control data transmission on the P frequency domain units. Since the CORESET is configured on only some of the P frequency domain units, the common signaling overhead can be reduced.

[0126] Before the RRC connection is established, the network may notify the CORESET configuration and CORESET cascade configuration through the SIB message. The CORESET configuration includes the frequency domain resources of the CORESET. The CORESET cascade configuration is used to instruct the terminal to perform cascading. The CORESET cascade configuration includes information required for the terminal to perform cascading, including but not limited to the identifier of the cascaded CORESET and the index of the CORESET used for cascading.

[0127] After the RRC connection is established, the network notifies the CORESET configuration and CORESET cascade configuration through the RRC message.

[0128] Optionally, if the network configures a CORESET that receives SIB information, such as CORESET 0, then the CORESET configuration and CORESET cascade configuration of each frequency domain unit need to be determined based on the MIB message and predefined rules. CORESET 0 typically only requires one configuration, which is common to all terminals.

[0129] In another implementation, the M frequency domain units are frequency domain units of the frequency band combination supported by the terminal. The terminal determines the CORESET of each frequency domain unit in the M frequency domain units for receiving the PDCCH. In this method, the CORESETs on different frequency domain units can be cascaded or not. Compared with the prior art, the CORESET on each frequency domain unit independently receives the PDCCH. The terminal can simultaneously use the CORESETs of multiple frequency domain units that can perform frequency band combination to receive the PDCCH, which is equivalent to increasing the bandwidth of the CORESET. It should be clear that in the embodiment of the present application, the terminal can be in any of the following states: idle state, inactive state, or RRC connected state.

[0130] In this implementation, the network needs to consider the capabilities of the terminal, that is, the network needs to consider the capabilities of the terminal when configuring M frequency domain units for the terminal device.

[0131] The frequency domain units of the frequency band combination supported by the terminal can also be described as frequency domain units related to the frequency band combination (bandcombination) capability of the terminal. The frequency band combination is also called the frequency band merging. The frequency band combination capability is used to indicate the number of frequency bands supported simultaneously by the terminal. A terminal may support one or more frequency bands simultaneously, and different terminals have different frequency band combination capabilities. The frequency domain units on all frequency bands supported by the terminal constitute the frequency domain units of the frequency band combination supported by the terminal. For example, if terminal 1 supports frequency band A and frequency band C, then the frequency band combination supported by terminal 1 is frequency band A and frequency band C, and the frequency domain units of the frequency band combination supported by terminal 1 are the frequency domain units on frequency band A and frequency band C supported by terminal 1.

[0132] Before the RRC connection is established, the network does not obtain the terminal's capability information. The network can pre-indicate the CORESET configuration and CORESET cascade configuration corresponding to a certain frequency band combination capability in the SIB based on prior information, such as the frequency bands of each frequency domain unit of the serving cell that support the frequency band combination. For example, if the serving cell supports different terminal types such as UE capabilities A, B, and C, the network can perform CORESET configuration and CORESET cascade configuration for at least one terminal capability.

[0133] After the RRC connection is established, the network has obtained the terminal's capability information. The network can configure the CORESET configuration and CORESET cascade configuration corresponding to a certain terminal type in the RRC message based on the terminal capability information and the frequency band combination capabilities supported by different terminals.

[0134] Optionally, if the network configures CORESET 0, the CORESET configuration and CORESET cascade configuration of each frequency domain unit needs to be determined according to MIB messages and predefined rules. There may be multiple CORESET 0s, which is equal to the number of frequency domain units of the frequency band combination indicated by the network and is common to terminals that support frequency domain unit merging.

[0135] When M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, and the terminal cascades CORESETs on different frequency domain units, it can be known that the terminal usually only supports some frequency bands according to the frequency band combination capability of the terminal, that is, the terminal only supports frequency domain units on some frequency bands, so M is usually less than P. When M is less than P, the PDCCH carried or sent on the cascaded CORESET is used to schedule data of the M frequency domain units, or the control information in the PDCCH carried or sent on the cascaded CORESET is used to control data transmission on the M frequency domain units. Without loss of generality, the network can also configure a CORESET of Q frequency domain units, where Q is less than or equal to M. The CORESET of these Q frequency domain units or the cascaded CORESET formed by the cascade of these Q frequency domain units can schedule data of the M frequency domain units.

[0136] In this embodiment, the terminal obtains configuration information of M frequency domain unit combinations based on the terminal capability, where M is less than or equal to the number P of frequency domain units configured in the terminal's serving cell, obtains frequency domain resources of the CORESETs on the M frequency domain unit combinations, and determines at least one CORESET for receiving the PDCCH based on the configuration information of the M frequency domain unit combinations and the frequency domain resources of the CORESETs. By configuring the CORESETs on some frequency domain units of the terminal's serving cell, the terminal capability can be matched, the common signaling overhead can be reduced, and the load balancing of each uplink UL / DL carrier can be achieved. By cascading all or some of the CORESETs on the M frequency domain unit combinations across frequency domain unit combinations, a CORESET for receiving the PDCCH can be obtained, so that the CORESET for receiving the PDCCH has a larger bandwidth, reduces the probability of PDCCH collision, increases the PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0137] Example 2

[0138] Based on Example 1, Example 2 of the present application provides a control channel transmission method. The implementation methods described in Example 1 can be applied to Example 2 and can achieve the same technical effects. This embodiment is described by taking the example of a terminal cascading M frequency domain unit CORESETs. Figure 7 is a flowchart of the control channel transmission method provided in Example 2 of the present application. As shown in Figure 7, the method provided in this embodiment includes the following steps.

[0139] S201. A terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.

[0140] In one implementation, the M frequency domain units may be any M frequency domain units in a serving cell of the terminal, that is, the M frequency domain units are frequency domain units irrelevant to the frequency band combining capability of the terminal.

[0141] In another implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

[0142] Band combination capability is a concept introduced in carrier aggregation (CA) technology. Band combination capability indicates the number of frequency bands supported simultaneously by a terminal. A terminal may support one or more frequency bands simultaneously, and different terminals have different band combination capabilities. For example, if terminal 1 only supports bands A and C, the band combination supported by terminal 1 is bands A and C. If terminal 2 only supports bands B and C, the band combination supported by terminal 2 is bands B and C. If terminal 3 only supports band C, the band combination supported by terminal 3 is band C. Accordingly, the network-side device can configure frequency domain units for cascading for the terminal based on the terminal's band combination capability. That is, the network-side device only configures CORESETs on frequency domain units on frequency bands supported by the terminal, and does not configure frequency domain units and CORESETs on frequency bands that the terminal does not support. Accordingly, the terminal device only cascades CORESETs on frequency bands it supports.

[0143] S202. The terminal obtains frequency domain resources of the CORESET on M frequency domain units.

[0144] S203: The terminal determines the order of CORESETs on the M frequency domain units.

[0145] In a first implementation, the terminal arranges the CORESETs on the M frequency domain units in ascending or descending order according to the starting frequencies of the CORESETs on the M frequency domain units, and cascades them according to a predefined cascading rule or as instructed by the network.

[0146] In the second implementation, the terminal arranges the CORESETs on the M frequency domain units in ascending or descending order according to the starting frequencies of the M frequency domain units, and cascades them according to a predefined cascading rule and as instructed by the network.

[0147] S204: The terminal cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET, which is used to receive the PDCCH.

[0148] When the M frequency domain units are any M frequency domain units in the serving cell of the terminal, or the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the following two methods can be used to cascade the CORESETs of the M frequency domain units.

[0149] In a first implementation manner, the terminal cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET according to the order of the CORESETs and a predefined cascade rule.

[0150] The predefined cascading rule may be sent by the network side device to the terminal, or may be pre-agreed between the network side device and the terminal.

[0151] Exemplarily, the predefined cascading rule may be: cascading all CORESETs configured on the network side to form a cascaded CORESET. The terminal then cascades the CORESETs on the M frequency domain units to form a cascaded CORESET according to the predefined rule and the order of the CORESETs on the M frequency domain units.

[0152] Since the CCEs in the cascaded CORESET need to be sorted, the terminal sorts the CORESETs on the M frequency domain units. The order of the CORESETs on the M frequency domain units can represent the order of the CCEs in the cascaded CORESET.

[0153] Figure 8 is a schematic diagram of a cascade of CORESETs of multiple frequency domain units. Referring to Figure 8, Figure 8 takes the frequency domain unit as BWP as an example. The service cell of the terminal is configured with three BWPs: BWP i, BWP j and BWP k. BWP i is located on carrier p of frequency band A, BWP j is located on carrier q of frequency band B, and BWP k is located on carrier m of frequency band C. A CORESET is configured on each BWP. The terminal sorts the CORESETs of the three BWPs and cascades them to form a cascaded CORESETm. The CCEs in the cascaded CORESETm are numbered 0-5. The order of the CCE numbers in the cascaded CORESETm corresponds to the starting frequency order of the three BWPs, or the starting frequency order of the CORESETs in the three BWPs.

[0154] Figure 9 shows another cascade diagram of CORESETs for multiple frequency domain units. The difference between Figure 9 and Figure 8 is that in Figure 9, no CORESET is configured for BWPi. That is, the network-side device only configures CORESETs for some of the BWPs configured in the terminal's serving cell, rather than for all BWPs. In Figure 9, the CCEs in the cascaded CORESETm are numbered 0-4.

[0155] Exemplarily, the predefined cascading rule may also be: selecting a CORESET with the same CORESET number from each frequency domain unit to cascade to form a cascaded CORESET.

[0156] Refer to Figure 10, which is another cascade diagram of CORESETs of multiple frequency domain units. In this method, the terminal first sorts the three BWPs according to their starting frequencies. When cascading, a CORESET with the same serial number is selected from the three BWPs each time according to the CORESET serial number from small to large or from large to small to form a cascade CORESET.

[0157] For example, first cascade CORESET sequence number 1, then the terminal selects CORESET with sequence number 1 from BWP i, BWP j and BWP k respectively: CORESETi_1, CORESETj_1 and CORESET k_1, CORESETi_1, CORESETj_1 and CORESET k_1 are cascaded to form cascade CORESET A. Then, the terminal selects CORESET with sequence number 2 from BWP i, BWP j and BWP k respectively: CORESETj_2 and CORESET k_2, CORESETj_2 and CORESET k_2 are cascaded to form cascade CORESET B. In this process, there is no CORESET with sequence number 2 in BWP i, so the CORESET of BWPi does not need to be cascaded. Finally, the terminal selects CORESET k_3, which is numbered 3, from BWP i, BWP j, and BWP k, respectively. CORESET k_3 is cascaded to form cascaded CORESET C. During this process, there is no CORESET 3 in BWP i and BWP j. Therefore, cascaded CORESET C is CORESET k_3, which is equivalent to no cascading.

[0158] In the second implementation manner, the terminal cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and the cascade indication information sent by the network side device. The cascade indication information includes the identifier of the cascaded CORESET and the index of the CORESET participating in the cascade in the M frequency domain units.

[0159] Optionally, the network side device may send the cascade indication information and the configuration information of the M frequency domain units to the terminal together, or may send the cascade indication information and the configuration information of the M frequency domain units to the terminal separately through different messages.

[0160] Taking the cascade schematic diagrams shown in FIG8 and FIG9 as an example, the cascade indication information includes a cascade CORESET identifier: cascade CORESET m, and the index of each CORESET participating in the cascade.

[0161] Taking the cascade diagram shown in Figure 10 as an example, the cascade indication information includes three cascade CORESET identifiers: cascade CORESET A, cascade CORESET B and cascade CORESET C, as well as the index of the CORESET participating in the cascade corresponding to each cascade CORESET identifier. For example, the index of the CORESET participating in the cascade corresponding to cascade CORESET A is: CORESETi_1, CORESETj_1 and CORESET k_1.

[0162] When the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the terminal needs to notify the network side of the frequency bands it supports before cascading, and then send or receive based on the frequency bands it supports in the frequency domain units on the frequency bands it supports. Alternatively, the network side directly notifies the terminal of the corresponding configuration of at least one capability level based on the candidate terminal capability level. In one way, the terminal can determine the frequency bands it supports based on its own frequency band combination capability, for example, before the RRC connection is established. In another way, the network side device indicates to the terminal the configuration corresponding to the frequency bands supported by the terminal, for example, after the RRC connection is established.

[0163] In the latter method, the network side device can carry the frequency band combination information in the cascade indication information, and the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal. Exemplarily, the frequency band combination information includes a combination identifier, and the combination identifier is used to indicate that the frequency bands supported by the terminal are combined. Optionally, the frequency band combination information also includes the identifier of the combined frequency band. For example, if the terminal supports frequency band A and frequency band C, the frequency band combination information also includes the identifier or frequency information of frequency band A and frequency band C.

[0164] Figure 11 is a schematic diagram of the cascade of CORESETs of frequency domain units of multiple terminals. Referring to Figure 11, terminal 1 only supports frequency bands A and C, terminal 2 only supports frequency bands B and C, and terminal 3 only supports frequency band C. The network-side device configures CORESETi1 of frequency band A and CORESET k1 of frequency band C for terminal 1, configures CORESET j1 of frequency band B and CORESET k2 of frequency band C for terminal 2, and configures CORESET k3 of frequency band C for terminal 3 based on the frequency band combination capabilities of each terminal.

[0165] Terminal 1, through network-side configuration parameters, can see CORESET i on frequency band A and CORESET k1 on frequency band C. It can concatenate CORESET i and CORESET k1 into a concatenated CORESET m, and Terminal 1 receives PDCCH on concatenated CORESET m. Terminal 2, through network-side configuration parameters, can see CORESET j1 on frequency band B and CORESET k2 on frequency band C. It can concatenate CORESET j1 and CORESET k2 into a concatenated CORESET n, and Terminal 2 receives PDCCH on concatenated CORESET n. Terminal 3, through network-side configuration parameters, can see CORESET k3 on frequency band C. Terminal 3 receives PDCCH on (concatenated) CORESET n k3.

[0166] Optionally, any one of the M frequency domain units is used to send downlink control information to improve flexibility. For example, in the frequency bands shown in Figures 8-11, the network-side device only sends SSBs in the frequency domain unit of frequency band C. The terminal can receive PDCCH on the CORESET of any frequency domain unit. In this case, the CORESETs of multiple frequency domain units do not need to be cascaded.

[0167] Optionally, the terminal does not expect at least one of the following configuration parameters of the cascaded CORESETs to be different:

[0168] Start symbol;

[0169] Number of continuous symbols;

[0170] CCE to REG mapping type;

[0171] Quasi-Colocation (QCL);

[0172] An indication of the presence of the Transmission Configuration Indication (TCI) field;

[0173] PDCCH-DMRS scrambling code identifier (Scrambling ID);

[0174] The associated search space type;

[0175] SCS;

[0176] CP.

[0177] The terminal does not expect at least one of the following configuration parameters of the cascaded CORESETs to be different, which can be understood as the UE expecting at least one of the following configuration parameters of the cascaded CORESETs to be the same.

[0178] The mapping type of CCE to REG is an interleaved type or a non-interleaved type. When the mapping type of CCE to REG used in the cascaded CORESET is an interleaved type, it can provide diversity gain and enhance PDCCH transmission reliability.

[0179] The TCI field presence indication is used to indicate whether a TCL field exists in the DCI.

[0180] The network tester can configure the search space for the cascade CORESET. The search space type associated with the cascade CORESET can be a public search space or a dedicated search space.

[0181] A cascaded CORESET may include one or more CORESETs. The search space associated with the cascaded CORESET refers to the search space of each CORESET included in the cascaded CORESET. The search spaces of each CORESET included in the cascaded CORESET can be the same or different. When the search spaces associated with the cascaded CORESET are different, the search spaces associated with the cascaded CORESET should meet predefined requirements, such as requirements related to the ability to monitor PDCCH based on time slots or spans.

[0182] The method of this embodiment can be used before or after an RRC connection is established. Before an RRC connection is established, the CORESET configuration information can be notified through the SIB. Before an RRC connection is established, the network-side device may not be able to obtain the capabilities of the terminal. Therefore, the network-side device needs to configure and cascade the CORESET on the frequency domain unit based on the prior information of the terminal capabilities supported by the frequency domain unit.

[0183] After the RRC connection is established, the CORESET configuration information can be notified through the RRC message. At this time, the network side device has obtained the terminal capabilities and can configure one or more CORESETs on a frequency domain unit. Therefore, the network side device can configure the frequency domain unit related to the frequency band combination capability of the terminal according to the terminal capabilities.

[0184] In this embodiment, the terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the terminal's serving cell. The terminal obtains frequency domain resources of the CORESETs on the M frequency domain units, determines the order of the CORESETs on the M frequency domain units, and cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET, which is used to receive the PDCCH. By configuring a CORESET on all or part of the frequency domain units of the terminal's serving cell, and cascading the configured CORESET cross-band units to form a cascaded CORESET, the PDCCH is received on the cascaded CORESET. The cascaded CORESET has a larger bandwidth, reduces the probability of PDCCH collision, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0185] Example 3

[0186] Embodiment 3 of the present application provides a control channel transmission method. The implementation methods described in Embodiments 1 and 2 can be applied to Embodiment 3 and achieve the same technical effects. Figure 12 is a flowchart of the control channel transmission method provided in Embodiment 3 of the present application. As shown in Figure 12, the method provided in this embodiment includes the following steps.

[0187] S301. The terminal obtains configuration information of M frequency domain units, where the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, and M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.

[0188] S302: The terminal obtains frequency domain resources of the CORESET on M frequency domain units.

[0189] S303: The terminal determines a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving the PDCCH.

[0190] Different from the solution in Example 2, in this embodiment, the CORESETs on the M frequency domain units of the frequency band combination supported by the terminal are not cascaded. Instead, the CORESETs on the M frequency domain units of the frequency band combination supported by the terminal are used as independent CORESETs. The terminal can use the CORESETs on the M frequency domain units to receive PDCCH at the same time, which is equivalent to increasing the frequency domain range of the CORESET used to receive PDCCH, thereby increasing transmission reliability and network flexibility. Furthermore, the probability of PDCCH conflict can be reduced and the PDCCH coverage capability can be improved.

[0191] Referring to Figure 13, Figure 13 is a schematic diagram of the CORESET of the frequency domain unit of the terminal. Assume that the frequency band combination capability of the terminal is: terminal 1 only supports frequency band A and frequency band C, terminal 2 only supports frequency band B and frequency band C, and terminal 3 only supports frequency band C. Then, the CORESET determined by terminal 1 for receiving PDCCH is CORESETi1 on frequency band A and CORESETk1 on frequency band C, the CORESET determined by terminal 2 for receiving PDCCH is CORESETj1 on frequency band B and CORESETk1 on frequency band C, and the CORESET determined by terminal 3 for receiving PDCCH is CORESETk1 on frequency band C.

[0192] Figure 13 takes the example of only one CORESET on each frequency band. Of course, there can be multiple CORESETs on each frequency band. When there are multiple CORESETs on the frequency band supported by the terminal, the terminal can select all or part of the multiple CORESETs for receiving PDCCH according to predefined rules, or determine all or part of the multiple CORESETs for receiving PDCCH according to the instruction of the network side device. For example, the network side device can indicate the index of the CORESET used to receive PDCCH.

[0193] Optionally, the number of CORESETs on any frequency domain unit in the frequency band combination supported by the terminal is not greater than the maximum number of CORESETs supported by the terminal, that is, the terminal does not expect the number of CORESETs on any frequency domain unit to be greater than the CORESET number capability supported by the terminal. The CORESET number capability supported by the terminal is the maximum number of CORESETs supported by the terminal. It can be understood that the maximum number of CORESETs supported by the terminal on different types of frequency domain units may be different. Taking BWP as an example, a maximum of 3 CORESETs can be configured on BWP, and the maximum number of CORESETs supported by the terminal is 3.

[0194] In this embodiment, the terminal obtains configuration information of M frequency domain units, where the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal, obtains frequency domain resources of the CORESET on the M frequency domain units, and determines the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving the PDCCH. In this embodiment, the terminal can simultaneously use the CORESETs on the M frequency domain units to receive the PDCCH, which is equivalent to increasing the frequency domain range of the CORESET used to receive the PDCCH, thereby increasing transmission reliability and network flexibility. Furthermore, it can reduce the probability of PDCCH collision and improve PDCCH coverage capability.

[0195] Example 4

[0196] Embodiment 4 of the present application provides a control channel transmission method, which is executed by a network side device. Figure 14 is a flowchart of the control channel transmission method provided by Embodiment 4 of the present application. As shown in Figure 14, the method provided in this embodiment includes the following steps.

[0197] S401. A network-side device sends configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal.

[0198] The configuration information of the M frequency domain units includes at least one of the following:

[0199] Frequency reference points of M frequency domain units;

[0200] A frequency offset value of each frequency domain unit in the M frequency domain units relative to the frequency reference point;

[0201] The SCS of each frequency domain unit in the M frequency domain units;

[0202] The CP of each frequency domain unit in the M frequency domain units;

[0203] The starting RB and size of each frequency domain unit in the M frequency domain units;

[0204] The index of each frequency domain unit in the M frequency domain units.

[0205] The value of M is less than or equal to P, that is, the network-side device can configure CORESET only on some frequency domain units of the serving cell, making the configuration of CORESET more flexible. The M frequency domain units can be any M frequency domain units in the serving cell of the terminal, or they can be frequency domain units of the frequency band combination supported by the terminal.

[0206] S402: The network-side device sends frequency domain resources of the CORESET on M frequency domain units to the terminal.

[0207] Optionally, the network side device may send the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to the terminal through the same message, or may send the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to the terminal through different messages.

[0208] One or more CORESETs can be configured on a frequency domain unit, and the frequency domain resources or time domain resources of multiple CORESETs in a frequency domain unit can overlap.

[0209] S403: The network-side device sends a PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0210] The network side device sends the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to the terminal, so that the terminal combines all or part of the CORESET cross-frequency domain units on the M frequency domain units to determine the CORESET for receiving the PDCCH. Similarly, the network side device also needs to combine all or part of the CORESET cross-frequency domain units on the M frequency domain units according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET to determine at least one CORESET for sending the PDCCH.

[0211] In one implementation, the network side device determines the order of the CORESETs on the M frequency domain units, cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET, and sends the PDCCH on the cascaded CORESET.

[0212] The method for the network side device to sort the CORESETs on the M frequency domain units refers to the method for sorting the terminals in the aforementioned embodiment, which will not be repeated here.

[0213] The network side device can cascade to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and a predefined cascade rule. The predefined rule can be negotiated by the network side device and the terminal, or determined by the network side device and sent to the terminal. Subsequently, the network side device and the terminal cascade the CORESETs on the M frequency domain units according to the predefined cascade rule.

[0214] Alternatively, the network-side device determines, based on some information, several cascaded CORESETs and the CORESETs participating in the cascade in the M frequency domain units. The network-side device generates cascade indication information, where the cascade indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units. The terminal-side device may cascade the CORESETs on the M frequency domain units according to the cascade indication information, and send the cascade indication information to the terminal, so that the terminal performs the cascade according to the cascade indication information.

[0215] When the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, optionally, the network side device may cascade the CORESETs on the M frequency domain units. The specific method for cascading used by the network side device refers to the method for cascading used by the terminal in the aforementioned embodiment and will not be repeated here. Optionally, the cascade indication information also includes frequency band combination information, which is used to indicate the frequency band combination of frequency domain units related to the frequency band combination capability of the terminal. When the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, optionally, the network side device may not cascade the CORESETs on the M frequency domain units, that is, the network side device may determine the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for sending PDCCH, and accordingly, the network side device sends PDCCH to the terminal on the CORESET of the M frequency domain units. In this way, the network side device only sends PDCCH on the frequency domain units of the frequency band combination supported by the terminal.

[0216] Optionally, the network side device sends downlink control information on some frequency domain units among the M frequency domain units. For example, the network side device sends downlink control information on only any one frequency domain unit among the M frequency domain units.

[0217] In this embodiment, the network-side device sends configuration information of M frequency domain units to the terminal, where M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal, sends frequency domain resources of the CORESET on the M frequency domain units to the terminal, and sends the PDCCH on at least one CORESET based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET. By configuring the CORESET on some frequency domain units of the serving cell of the terminal, the network-side device can reduce common signaling overhead and achieve load balancing of each uplink UL / DL carrier. The network-side device combines all or some of the CORESETs on the M frequency domain units across frequency domain units to obtain a CORESET for sending the PDCCH, so that the CORESET used for sending the PDCCH has a larger bandwidth, reduces the probability of PDCCH collision, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0218] Example 5

[0219] Based on the above embodiments, the fifth embodiment of the present application provides a control channel transmission method. This embodiment is used to describe the signaling interaction between the terminal and the network-side device during the control channel transmission process. Figure 15 is a signaling flow chart of the control channel transmission method provided in the fifth embodiment of the present application. As shown in Figure 15, the method provided in this embodiment includes the following steps.

[0220] S501: A network-side device sends configuration information of M frequency domain units to a terminal.

[0221] Here, M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal.

[0222] S502: The network-side device sends frequency domain resources of the CORESET on M frequency domain units to the terminal.

[0223] S503: The network-side device determines at least one CORESET for sending the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0224] S504: The terminal device determines at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0225] There is no specific order in which steps S503 and S504 are executed, and they can also be executed simultaneously.

[0226] S505: The network-side device sends a PDCCH on the determined at least one CORESET.

[0227] S506: The terminal receives the PDCCH on the determined at least one CORESET.

[0228] The specific implementation of this embodiment refers to the description of the above embodiment and will not be repeated here.

[0229] Example 6

[0230] The control channel transmission method provided in the embodiment of the present application can be executed by a control channel transmission device. In the embodiment of the present application, the control channel transmission device provided in the embodiment of the present application is described by taking a method for executing control channel transmission by a control channel transmission device as an example.

[0231] Figure 16 is a structural diagram of a control channel transmission device provided in Example 6 of the present application. The device can be used in a terminal. As shown in Figure 16, the control channel transmission device 100 provided in this embodiment includes the following modules.

[0232] An acquisition module 11 is configured to acquire configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal;

[0233] The acquisition module 11 is further configured to acquire frequency domain resources of the CORESET on the M frequency domain units;

[0234] The determination module 12 is configured to determine at least one CORESET for receiving the PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0235] In an optional implementation, the determining module 12 is specifically configured to:

[0236] Determining an order of CORESETs on the M frequency domain units;

[0237] According to the order of the CORESETs on the M frequency domain units, at least one cascaded CORESET is formed by cascading, and the cascaded CORESET is used to receive the PDCCH.

[0238] In an optional implementation, the determining module 12 is specifically configured to:

[0239] The CORESETs on the M frequency domain units are arranged in ascending or descending order according to the starting frequencies of the CORESETs on the M frequency domain units or the starting frequencies of the M frequency domain units.

[0240] In another optional implementation, the determining module 12 is specifically configured to:

[0241] The M frequency domain units are arranged in ascending or descending order according to starting frequencies of the M frequency domain units.

[0242] In an optional implementation, the determining module 12 is specifically configured to:

[0243] According to the order of the CORESETs on the M frequency domain units and a predefined cascading rule, at least one cascaded CORESET is formed by cascading.

[0244] In another optional implementation, the determining module is specifically configured to:

[0245] According to the order of the CORESETs on the M frequency domain units and the cascade indication information sent by the network side device, at least one cascade CORESET is cascaded to form the cascade, where the cascade indication information includes an identifier of the cascade CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.

[0246] In an optional implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

[0247] In an optional implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;

[0248] The cascade indication information further includes frequency band combination information, where the frequency band combination information is used to indicate the frequency band combination of frequency domain units related to the frequency band combination capability of the terminal.

[0249] In an optional implementation, the terminal does not expect at least one of the following configuration parameters of the cascaded CORESET to be different:

[0250] Start symbol;

[0251] Number of continuous symbols;

[0252] CCE to REG mapping type;

[0253] QCL;

[0254] An indication of the presence of a TCI domain;

[0255] PDCCH-DMRS-ScramblingID;

[0256] The associated search space type;

[0257] SCS;

[0258] CP.

[0259] In an optional implementation, the CCE to REG mapping type adopted in the cascaded CORESET is an interleaved type.

[0260] In an optional implementation manner, the search spaces of the CORESETs included in the cascaded CORESET are the same or different.

[0261] In an optional implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;

[0262] The determining module 12 is specifically configured to determine a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving the PDCCH.

[0263] In an optional implementation manner, the number of CORESETs on any frequency domain unit of the frequency band combination supported by the terminal is not greater than the maximum number of CORESETs supported by the terminal.

[0264] In an optional implementation manner, the configuration information of the M frequency domain units includes at least one of the following:

[0265] Frequency reference points of the M frequency domain units;

[0266] A frequency offset value of each frequency domain unit in the M frequency domain units relative to the frequency reference point;

[0267] An SCS of each frequency domain unit in the M frequency domain units;

[0268] A CP of each frequency domain unit in the M frequency domain units;

[0269] A starting resource block (RB) and size of each frequency domain unit in the M frequency domain units;

[0270] The index of each frequency domain unit in the M frequency domain units.

[0271] In an optional implementation, the frequency reference points of the M frequency domain units include at least one of the following:

[0272] There is no frequency reference point of a frequency domain unit associated with a CD-SSB in the M frequency domain units;

[0273] A common frequency reference point of a frequency domain unit not associated with a CD-SSB among the M frequency domain units;

[0274] A frequency reference point of each frequency domain unit in the M frequency domain units;

[0275] A common frequency reference point of the M frequency domain units.

[0276] In an optional implementation manner, any one frequency domain unit among the M frequency domain units is used to send downlink control information.

[0277] In an optional implementation, the M frequency domain units include at least one of the following units: a BWP, a carrier, or a frequency band.

[0278] The network-side device can reduce public signaling overhead and achieve load balancing of each uplink UL / DL carrier by configuring CORESET on some frequency domain units of the terminal's service cell. The terminal obtains a CORESET for receiving PDCCH by combining all or part of the CORESET cross-frequency domain units on M frequency domain units, so that the CORESET used to receive PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0279] Example 7

[0280] Embodiment 7 of the present application provides a control channel transmission device, which can be used in network-side equipment. Figure 17 is a structural diagram of a control channel transmission device provided in Embodiment 7 of the present application. As shown in Figure 17, the control channel transmission device 200 provided in this embodiment includes the following modules.

[0281] A sending module 21 is configured to send configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal;

[0282] The sending module 21 is configured to send the frequency domain resources of the CORESET on the M frequency domain units to the terminal;

[0283] The processing module 22 is configured to send a PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0284] In an optional implementation, the processing module 22 is specifically configured to:

[0285] Determining an order of CORESETs on the M frequency domain units;

[0286] Cascading the CORESETs on the M frequency domain units to form at least one cascaded CORESET;

[0287] The PDCCH is sent on the cascaded CORESET.

[0288] In an optional implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

[0289] In an optional implementation, the sending module 21 is further configured to:

[0290] Sending cascade indication information to the terminal, where the cascade indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.

[0291] In an optional implementation, when the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the cascade indication information also includes frequency band combination information, and the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.

[0292] In an optional implementation manner, the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal;

[0293] The processing module 22 is specifically configured to:

[0294] Determine a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for sending a PDCCH;

[0295] The PDCCH is sent to the terminal on the CORESET of the M frequency domain units.

[0296] The network-side device can reduce public signaling overhead and achieve load balancing of each uplink UL / DL carrier by configuring CORESET on some frequency domain units of the terminal's service cell. The network-side device combines all or part of the CORESETs on M frequency domain units across frequency domain units to obtain a CORESET for sending PDCCH, so that the CORESET used to send PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0297] The transmission device of the control channel in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0298] The transmission device of the control channel provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 15 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0299] As shown in Figure 18, an embodiment of the present application further provides a communication device 300, including a processor 31 and a memory 32. The memory 32 stores a program or instruction that can be run on the processor 31. For example, when the communication device 300 is a terminal, the program or instruction, when executed by the processor 31, implements the various steps of the method embodiments of Figures 2 to 13 above, and can achieve the same technical effects. When the communication device 300 is a network-side device, the program or instruction, when executed by the processor 31, implements the various steps of the method embodiment of Figure 14 above, and can achieve the same technical effects. To avoid repetition, they are not repeated here.

[0300] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiments shown in Figures 2-13. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 19 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0301] The terminal 400 includes but is not limited to: a radio frequency unit 41, a network module 42, an audio output unit 43, an input unit 44, a sensor 45, a display unit 46, a user input unit 47, an interface unit 48, a memory 49 and at least some of the components of the processor 410.

[0302] Those skilled in the art will appreciate that terminal 400 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to processor x 10 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG19 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components or arrange the components differently, which will not be described in detail here.

[0303] It should be understood that in an embodiment of the present application, the input unit 44 may include a graphics processing unit (GPU) 441 and a microphone 442, and the graphics processor 441 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 46 may include a display panel 461, and the display panel 461 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 47 includes a touch panel 471 and at least one of other input devices 472. The touch panel 471 is also called a touch screen. The touch panel 471 may include two parts: a touch detection device and a touch controller. Other input devices 472 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0304] In the embodiment of the present application, after receiving downlink data from the network-side device, the RF unit 41 can transmit the data to the processor 410 for processing. In addition, the RF unit 41 can send uplink data to the network-side device. Generally, the RF unit 41 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0305] The memory 49 can be used to store software programs or instructions and various data. The memory 49 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 49 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 49 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0306] Processor 410 may include one or more processing units. Optionally, processor 410 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 410.

[0307] Among them, the processor 410 is used to obtain configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the service cell of the terminal; obtain the frequency domain resources of the control resource set CORESET on the M frequency domain units; and determine at least one CORESET for receiving PDCCH based on the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

[0308] By configuring CORESET on some frequency domain units of the terminal's service cell, public signaling overhead can be reduced and load balancing of each uplink UL / DL carrier can be achieved. By combining all or part of the CORESET cross-frequency domain units on M frequency domain units, a CORESET for receiving PDCCH is obtained, so that the CORESET for receiving PDCCH has a larger bandwidth, reduces the probability of PDCCH conflict, increases PDCCH coverage capability and transmission reliability, and increases network flexibility.

[0309] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment Figures 2 to 13, and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0310] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG14 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0311] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 20, the network-side device 500 includes an antenna 51, a radio frequency device 52, a baseband device 53, a processor 54, and a memory 55. The antenna 51 is connected to the radio frequency device 52. In the uplink direction, the radio frequency device 52 receives information via the antenna 51 and sends the received information to the baseband device 53 for processing. In the downlink direction, the baseband device 53 processes the information to be transmitted and sends it to the radio frequency device 52. The radio frequency device 52 processes the received information and then sends it through the antenna 51.

[0312] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 53 , which includes a baseband processor.

[0313] The baseband device 53 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 20, one of which is, for example, a baseband processor, which is connected to the memory 55 through a bus interface to call the program in the memory 55 and execute the network side device operations shown in the above method embodiment.

[0314] The network side device may further include a network interface 56, which is, for example, a Common Public Radio Interface (CPRI).

[0315] Specifically, the network side device 500 of the embodiment of the present application also includes: instructions or programs stored in the memory 55 and can be run on the processor 54. The processor 54 calls the instructions or programs in the memory 55 to execute the method of execution of each module shown in Figure 17 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0316] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the method embodiments shown in Figures 2 to 14 above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0317] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0318] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiments shown in Figures 2 to 14 above, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0319] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0320] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned control channel transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0321] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method shown in Figures 2 to 13 as described above, and the network side device can be used to execute the steps of the method shown in Figure 14 as described above.

[0322] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0323] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0324] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A control channel transmission method, wherein: include: The terminal obtains configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal; The terminal obtains frequency domain resources of a control resource set CORESET on the M frequency domain units; The terminal determines at least one CORESET for receiving a physical downlink control channel PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

2. The method according to claim 1, wherein: The terminal determines, according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, at least one CORESET for receiving a physical downlink common control channel PDCCH, including: The terminal determines an order of CORESETs on the M frequency domain units; The terminal cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units, and the cascaded CORESET is used to receive the PDCCH.

3. The method according to claim 2, wherein: The terminal determines the order of CORESETs on the M frequency domain units, including: The terminal arranges the CORESETs on the M frequency domain units in ascending or descending order according to the starting frequencies of the CORESETs on the M frequency domain units or the starting frequencies of the M frequency domain units.

4. The method according to claim 2 or 3, wherein: The terminal cascades at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units, including: The terminal cascades to form at least one cascaded CORESET according to the order of the CORESETs on the M frequency domain units and a predefined cascade rule or cascade indication information sent by a network side device, wherein the cascade indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.

5. The method according to any one of claims 2 to 4, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

6. The method according to claim 4, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal; The cascade indication information also includes frequency band combination information, where the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.

7. The method according to any one of claims 2 to 6, wherein: The terminal does not expect at least one of the following configuration parameters of the cascaded CORESET to be different: Start symbol; Number of continuous symbols; The mapping type of control channel elements CCE to resource element groups REG; Quasi co-location relationship QCL; An indication of the presence of the transmission configuration indication TCI field; PDCCH-DMRS-ScramblingID; The associated search space type; Subcarrier spacing SCS; Cyclic prefix CP.

8. The method according to claim 1, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal; The terminal determines, according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, at least one CORESET for receiving a physical downlink control channel PDCCH, including: The terminal determines a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for receiving a PDCCH.

9. The method according to any one of claims 1 to 8, wherein: The configuration information of the M frequency domain units includes at least one of the following: The frequency reference points of the M frequency domain units; A frequency offset value of each frequency domain unit in the M frequency domain units relative to the frequency reference point; The SCS of each frequency domain unit in the M frequency domain units; A CP of each frequency domain unit in the M frequency domain units; A starting resource block RB and a size of each frequency domain unit in the M frequency domain units; An index of each frequency domain unit in the M frequency domain units.

10. A control channel transmission method, wherein: include: The network side device sends configuration information of M frequency domain units to the terminal, where M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal; The network side device sends the frequency domain resources of the control resource set CORESET on the M frequency domain units to the terminal; The network side device sends a physical downlink control channel PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

11. The method according to claim 10, wherein: The network side device sends a downlink control channel PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, including: The network side device determines the order of CORESETs on the M frequency domain units; The network side device cascades the CORESETs on the M frequency domain units to form at least one cascaded CORESET; The network side device sends the PDCCH on the cascaded CORESET.

12. The method according to claim 11, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

13. The method according to claim 11 or 12, wherein: Also includes: The network side device sends cascading indication information to the terminal, where the cascading indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.

14. The method according to claim 13, wherein: When the M frequency domain units are frequency domain units of a frequency band combination supported by the terminal, the cascade indication information also includes frequency band combination information, and the frequency band combination information is used to indicate the frequency band combination of the frequency domain units related to the frequency band combination capability of the terminal.

15. The method according to claim 10, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal; The network side device sends a downlink control channel PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET, including: The network side device determines the CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for sending the PDCCH; The network side device sends the PDCCH to the terminal on the CORESET of the M frequency domain units.

16. A transmission device for a control channel, wherein: include: An acquisition module, used to acquire configuration information of M frequency domain units, where M is less than or equal to the number P of frequency domain units configured in the serving cell of the terminal; The acquisition module is further used to acquire the frequency domain resources of the control resource set CORESET on the M frequency domain units; The determination module is used to determine at least one CORESET for receiving a physical downlink control channel PDCCH according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

17. The device according to claim 16, wherein: The determination module is specifically used for: Determining the order of CORESETs on the M frequency domain units; According to the order of the CORESETs on the M frequency domain units, at least one cascaded CORESET is formed by cascading, and the cascaded CORESET is used to receive the PDCCH.

18. The device according to claim 17, wherein: The determination module is specifically used for: According to the starting frequencies of the CORESETs on the M frequency domain units or the starting frequencies of the M frequency domain units, the CORESETs on the M frequency domain units are arranged in ascending order or descending order.

19. The device according to claim 17 or 18, wherein: The determination module is specifically used for: According to the order of the CORESETs on the M frequency domain units, and the predefined cascading rule or the cascading indication information sent by the network side device, at least one cascaded CORESET is cascaded to form the cascade, and the cascade indication information includes the identifier of the cascaded CORESET and the index of the CORESET participating in the cascade in the M frequency domain units.

20. The device according to any one of claims 17 to 19, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

21. The device according to any one of claims 17 to 20, wherein: The terminal does not expect at least one of the following configuration parameters of the cascaded CORESET to be different: Start symbol; Number of continuous symbols; The mapping type of control channel elements CCE to resource element groups REG; Quasi co-location relationship QCL; An indication of the presence of the transmission configuration indication TCI field; PDCCH-DMRS-ScramblingID; The associated search space type; Subcarrier spacing SCS; Cyclic prefix CP.

22. The device according to claim 17, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal; The determination module is specifically used for: A CORESET of each frequency domain unit in the M frequency domain units is determined as an independent CORESET for receiving the PDCCH.

23. A transmission device for a control channel, wherein: include: A sending module, configured to send configuration information of M frequency domain units to a terminal, where M is less than or equal to the number P of frequency domain units configured in a serving cell of the terminal; The sending module is used to send the frequency domain resources of the control resource set CORESET on the M frequency domain units to the terminal; The processing module is used to send a physical downlink control channel PDCCH on at least one CORESET according to the configuration information of the M frequency domain units and the frequency domain resources of the CORESET.

24. The device according to claim 23, wherein: The processing module is specifically used for: Determining the order of CORESETs on the M frequency domain units; According to the order of the CORESETs on the M frequency domain units, cascading to form at least one cascaded CORESET; The PDCCH is sent on the cascaded CORESET.

25. The device according to claim 24, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal.

26. The device according to claim 24 or 25, wherein: The sending module is also used for: Sending cascade indication information to the terminal, where the cascade indication information includes an identifier of the cascaded CORESET and an index of the CORESET participating in the cascade in the M frequency domain units.

27. The device according to claim 23, wherein: The M frequency domain units are frequency domain units of a frequency band combination supported by the terminal; The processing module is specifically used for: Determine a CORESET of each frequency domain unit in the M frequency domain units as an independent CORESET for sending a PDCCH; The PDCCH is sent to the terminal on the CORESET of the M frequency domain units.

28. A terminal, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the control channel transmission method as claimed in any one of claims 1 to 9 are implemented.

29. A network side device, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the control channel transmission method as claimed in any one of claims 10 to 15 are implemented.

30. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the control channel transmission method as described in any one of claims 1-9, or implements the steps of the control channel transmission method as described in any one of claims 10 to 15.

Images