Wireless communication method and apparatuses, and device

By determining the time-frequency domain resources and resource mapping method of the target CORESET, the problem of insufficient CORESET performance was solved, and the coverage of control information and terminal capacity were improved.

WO2026103802A1PCT designated stage Publication Date: 2026-05-21VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
VIVO MOBILE COMM CO LTD
Filing Date
2025-11-13
Publication Date
2026-05-21

AI Technical Summary

Technical Problem

In the prior art, the performance of the control resource set (CORESET) is insufficient, resulting in limited coverage of control information and limited terminal capacity in the communication system.

Method used

By determining the time-frequency domain resources of the target control resource set CORESET and/or the resource mapping method of the target CORESET based on the first information, including the resource information of the target frequency domain unit, the resource indication information of the CORESET, the resource mapping information of the CORESET, the aggregation level of the CORESET, the terminal capability and the frequency domain range, the resources of the CORESET are expanded and its performance is improved.

Benefits of technology

This improves the coverage of control information in the communication system and the capacity of terminals within the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025134695_21052026_PF_FP_ABST
    Figure CN2025134695_21052026_PF_FP_ABST
Patent Text Reader

Abstract

The present application belongs to the field of communications. Disclosed in the present application are wireless communication method and apparatuses, and a device. The wireless communication method in the embodiments of the present application comprises: a communication device determines a time-frequency domain resource of a target CORESET and / or a resource mapping mode of the target CORESET on the basis of first information, wherein the first information comprises at least one of the following: resource information of a target frequency domain unit, CORESET resource indication information, CORESET resource mapping information, a CORESET aggregation level, a terminal capability, a frequency domain range and a service type.
Need to check novelty before this filing date? Find Prior Art

Description

Wireless communication methods, apparatus and equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411637520.3, filed on November 15, 2024, entitled "Wireless Communication Method, Apparatus and Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a wireless communication method, apparatus, and device. Background Technology

[0004] In related technologies, the Control Resource Set (CORESET) is used to describe the frequency domain characteristics of blind detection resources of the Physical Downlink Control Channel (PDCCH). However, the performance of CORESET is currently insufficient, which limits the coverage of control information (such as PDCCH) in the communication system and the capacity of terminals accessed within the communication system. How to improve the performance of CORESET is a problem that needs to be solved. Summary of the Invention

[0005] This application provides a wireless communication method, apparatus, and device that can solve the problem of insufficient performance of CORESET.

[0006] Firstly, a wireless communication method is provided, comprising:

[0007] The communication device determines the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information;

[0008] The first information includes at least one of the following:

[0009] Resource information of the target frequency domain unit, resource indication information of CORESET, resource mapping information of CORESET, aggregation level of CORESET, terminal capabilities, frequency domain range, and service type.

[0010] Secondly, a wireless communication device is provided, comprising:

[0011] The processing module is used to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information;

[0012] The first information includes at least one of the following:

[0013] Resource information of the target frequency domain unit, resource indication information of CORESET, resource mapping information of CORESET, aggregation level of CORESET, terminal capabilities, frequency domain range, and service type.

[0014] Thirdly, a wireless communication device is provided, the wireless communication device being configured to perform the steps of the method described in the first aspect.

[0015] Fourthly, a communication device is provided, the communication device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0016] Fifthly, a communication device is provided, including a processor and a communication interface;

[0017] The processor is used to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information;

[0018] The first information includes at least one of the following:

[0019] Resource information of the target frequency domain unit, resource indication information of CORESET, resource mapping information of CORESET, aggregation level of CORESET, terminal capabilities, frequency domain range, and service type.

[0020] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0021] In a seventh aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, or the network-side device can be used to perform the steps of the method as described in the first aspect.

[0022] Eighthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0023] In a ninth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the wireless communication method as described in the first aspect.

[0024] In this embodiment, the communication device determines the time-frequency domain resources and / or resource mapping method of the target CORESET based on first information. The first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type. Specifically, by determining the time-frequency domain resources and / or resource mapping method of the target CORESET based on the first information (at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type), the communication device can expand the resources of the CORESET (e.g., expand the resources of the CORESET within the target frequency domain unit), and / or expand the granularity of the frequency domain resource indication of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET. This can improve the performance of the CORESET, thereby increasing the coverage of control information in the communication system and increasing the capacity of terminals within the communication system. Attached Figure Description

[0025] Figure 1 is a schematic diagram of a communication system architecture provided in an embodiment of this application.

[0026] Figure 2 is a schematic diagram of a non-interleaved mapping provided in this application.

[0027] Figure 3 is a schematic diagram of an interleaving mapping provided in this application.

[0028] Figure 4 is a schematic flowchart of a wireless communication method provided according to an embodiment of this application.

[0029] Figures 5 to 28 are schematic diagrams of the target CORESET provided according to the embodiments of this application.

[0030] Figure 29 is a schematic block diagram of a wireless communication device according to an embodiment of this application.

[0031] Figure 30 is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0032] Figure 31 is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application.

[0033] Figure 32 is a schematic block diagram of a network-side device provided according to an embodiment of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0035] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0036] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0037] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0038] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. Specifically, the wireless communication system includes a terminal 11 and a network-side device 12. The communication device described in this embodiment can be either the terminal 11 or the network-side device 12.

[0039] Terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home device (home device with wireless communication function, such as refrigerator, television, washing machine or furniture), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0040] Among them, network-side equipment 12 may include access network equipment or core network equipment.

[0041] Alternatively, access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, wireless local area network (WLAN) access points (APs), or wireless Fidelity (WiFi) nodes, etc. The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), 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, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0042] Optionally, core network equipment may also be referred to as core network nodes, core network functions, or core network elements, and includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0043] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0044] To better understand the technical solution of this application, the control channel structure is described below.

[0045] A control resource set (CORESET) can be defined as: a set of resource-element groups (REGs) under a given numerology.

[0046] A resource element group (REG) can be defined as a resource block (RB) in an orthogonal frequency-division multiplexing (OFDM) symbol.

[0047] A REG bundle can be defined as a set of several REG(s). The size of a REG bundle can be {2, 3, 6}, which is related to the number of OFDM symbols in the CORESET. REG bundles are mainly involved in precoding and channel estimation. 1 CCE = 6 REGs.

[0048] Aggregation Level (AL): A PDCCH consists of several control channel elements (CCEs). Currently supported aggregation levels are {1, 2, 4, 8, 16}.

[0049] CORESET can be used to describe the frequency domain characteristics of PDCCH blind detection resources. The search space represents the time domain characteristics, namely the period and offset, the number of time slots monitored in each period, and the starting symbol in each time slot.

[0050] CORESET's CCE-to-REG mapping includes two methods: interleaved mapping and non-interleaved mapping. Both methods map at the REG bundle granularity.

[0051] Within a series of PRBs in the CORESET frequency domain, the terminal (UE) attempts to blindly detect downlink control information (DCI) within these PRBs.

[0052] Resources within a CORESET are grouped into groups of six consecutive PRBs. Different PRB groups can be consecutive or non-consecutive.

[0053] A CORESET can occupy one or more consecutive symbols in the time domain: {1,2,3}.

[0054] When there is only one symbol, the REG bundle size can be {2, 6}.

[0055] When there are 2 / 3 symbols, the REG bundle size can be equal to the number of time-domain symbols or 6.

[0056] A UE can be configured with one or more CORESETs, with a maximum of 3 CORESETs per cell per Band Width Part (BWP).

[0057] Each CORESET can be associated with two types of search spaces: the Common Search Space (CSS) or the User Specific Search Space (USS).

[0058] Each BWP can have a maximum of 3 CORESETs;

[0059] Each BWP can have a maximum of 10 search spaces.

[0060] Multiple CORESETs configured in a UE can overlap in the frequency domain or time domain.

[0061] Within each CORESET, the mapping from CCE to REG can be interleaved or non-interleaved, but a CORESET can only have one mapping method.

[0062] If it is a non-interleaved mapping, an exemplary mapping method can be shown in Figure 2.

[0063] If it is interleaved, for the CORESET of the 1 symbol (that is...) L∈{2,6}, for symbols of 2 or 3

[0064] An interleaver or interleaving function is defined as: x=cR+rr=0,1,…,R-1 c=0,1,…,C-1

[0065] Where R∈{2,3,6}, R is the interleaver size.

[0066] The terminal (UE) does not expect to process configuration information, resulting in the value of the interleaving parameter C not being an integer (that is, the network configuration guarantees that the obtained interleaving parameter C is an integer).

[0067] If it is an interleaved mapping, an exemplary mapping method can be shown in Figure 3.

[0068] The wireless communication method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0069] Figure 4 is a schematic flowchart of a wireless communication method 200 according to an embodiment of this application. As shown in Figure 4, the wireless communication method 200 may include at least some of the following:

[0070] S210, the communication device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information; wherein, the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type.

[0071] It should be understood that Figure 4 illustrates the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and other operations or variations of the operations shown in Figure 4 may also be performed in this application.

[0072] In some embodiments, the communication device may be a terminal and / or a network-side device.

[0073] In some embodiments, the target frequency domain unit may include, but is not limited to, one of the following:

[0074] Spectrum, band, subband, frequency part, bandwidth (BWP), a continuous segment of frequency domain resources (e.g., several consecutive PRBs).

[0075] For example, the target frequency domain element can be a non-terrestrial network (NTN) frequency band, such as S band, L band, Ka band, Ku band, etc.

[0076] For example, the target frequency domain unit can be a frequency domain range, such as FR 1, FR2, FR 3, etc.

[0077] The target CORESET described in the embodiments of this application can be used to transmit control channels (such as Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Physical Sidelink Control Channel (PSCCH), etc.). The target CORESET described in the embodiments of this application can also be used to transmit data channels (such as Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), etc.).

[0078] The target frequency domain unit described in the embodiments of this application can also be referred to as (small) bandwidth.

[0079] In some embodiments, the target CORESET is located within one or more target frequency domain units, thereby expanding the resources of the CORESET within the target frequency domain unit.

[0080] It should be noted that for a 5MHz bandwidth, if the subcarrier spacing (SCS) is configured to 30kHz, there are 11 PRBs. However, the CORESET frequency domain configuration granularity is 6 PRBs. Within these 11 PRBs, only 6 PRBs can be configured for the CORESET. In this case, since the number of configurable aggregation levels for the CCE is 1, 2, 4, 8, or 16, within a 6PRB CORESET, if the number of OFDM symbols configured in the time domain is 3, the maximum configurable aggregation level (AL) within the CORESET is 2, resulting in limited PDCCH coverage, i.e., reduced cell coverage. Similarly, for other smaller bandwidths (such as 1.4MHz, 3MHz, or other sizes), there is also the problem of insufficient CORESET resources or insufficient PDCCH resources leading to limited PDCCH coverage. Furthermore, insufficient CORESET resources also limit the number of UEs that can access the network. On the one hand, for low-bandwidth scenarios, it is necessary to consider increasing the coverage of control information (such as PDCCH) within the communication system, as well as the number of UEs accessing the system, i.e., the UE capacity within the system, and increasing the capacity of control information within the communication system. On the other hand, if bandwidth is increased through (low)bandwidth aggregation, it is necessary to design the interleaving method of control information (such as PDCCH) to improve the coverage of control information (such as PDCCH) within the communication system and the UE capacity within the system.

[0081] Based on the aforementioned technical problems, in the embodiments of this application, the communication device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information (at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type). This can expand the resources of the CORESET (such as expanding the resources of the CORESET within the target frequency domain unit), and / or expand the frequency domain resource indication granularity of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET, thereby improving the performance of the CORESET, increasing the coverage of control information in the communication system, and increasing the capacity of terminals within the communication system.

[0082] In some implementations, the communication device can determine the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the frequency range (FR). Specifically, for example, the number of OFDM symbols that a CORESET can configure differs depending on the FR. For instance, for FR1, the number of OFDM symbols that a CORESET can configure is Y1; for FR2, the number of OFDM symbols that a CORESET can configure is Y2. Alternatively, the number of OFDM symbols that a CORESET can configure can be determined based on the bands supported by the UE. Specifically, in L band, S band, Ka band, Ku band, unlicensed frequency bands, bands supporting carrier aggregation (CA), bands supporting dual connection (DC), etc., the number of OFDM symbols that can be configured can be independently.

[0083] In some implementations, the communication device can determine the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the service type. Specifically, for example, the number of OFDM symbols that a CORESET can configure varies depending on the service type. For instance, for NTN services, the number of OFDM symbols that a CORESET can configure is Y3 (e.g., Y3=4); for cellular networks, the number of OFDM symbols that a CORESET can configure is Y4. As another example, for Low Power Wide Coverage (LPWA) services, the number of OFDM symbols that a CORESET can configure can be configured independently.

[0084] In some embodiments, the resource mapping information of the CORESET includes at least one of the following:

[0085] Mapping method, mapping order;

[0086] The mapping method includes at least one of the following: interleaved mapping method and non-interleaved mapping method.

[0087] The mapping order described in the embodiments of this application can be understood as mapping resources in a certain order. The mapping order described in the embodiments of this application can also be called sequential mapping, and this application does not limit it in this way.

[0088] Optionally, the resource mapping information of CORESET can be configured by the network side, or the resource mapping information of CORESET can be agreed upon by the protocol.

[0089] In some embodiments, the resource information of the target frequency domain unit includes the bandwidth of the target frequency domain unit and / or the location of the target frequency domain unit. Specifically, for example, the communication device can determine the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the bandwidth of the target frequency domain unit and / or the location of the target frequency domain unit, and can expand the resources of the CORESET within the target frequency domain unit.

[0090] In some embodiments, the time-frequency domain resources of the target CORESET include at least one of the following:

[0091] N1 sub-time domain resources, N2 sub-frequency domain resources;

[0092] N1 is an integer greater than 1, and N2 is an integer greater than 1.

[0093] In this embodiment, the time-domain resources of the target CORESET are divided into N1 sub-time-domain resources. The time-domain resources of the target CORESET can be block-mapped (such as interleaved mapping or non-interleaved mapping), thereby expanding the time-domain resources of the CORESET.

[0094] It should be noted that the i-th sub-time domain resource mentioned in the embodiments of this application can refer to the i-th sub-time domain resource among the N1 sub-time domain resources, where i is a positive integer and 1≤i≤N1.

[0095] In this embodiment, the frequency domain resources of the target CORESET are divided into N2 sub-frequency domain resources. The frequency domain resources of the target CORESET can be block-mapped (such as interleaved mapping or non-interleaved mapping), thereby expanding the frequency domain resources of the CORESET.

[0096] In some embodiments, the temporal resource size of the target CORESET is K (e.g., K = 4), where K / N1 is an integer greater than or equal to 0, and K is an integer greater than or equal to 0.

[0097] In some embodiments, the target CORESET includes at least two CORESET parts or at least two CORESET part groups, wherein a CORESET part group includes at least two CORESET parts.

[0098] It should be noted that a CORESET part can be a portion of the time-frequency domain resources in the target CORESET. The time-domain resources within a CORESET part can be continuous or discontinuous, and the frequency-domain resources within a CORESET part can be continuous or discontinuous.

[0099] For example, taking the target frequency domain unit as spectrum and N1=2 as an example, the two sub-time domain resources include the first sub-time domain resource and the second sub-time domain resource. If the target CORESET is located within a spectrum, the first sub-time domain resource and all frequency domain resources can be the CORESET part 1 in the target CORESET, and the second sub-time domain resource and all frequency domain resources can be the CORESET part 2 in the target CORESET.

[0100] For example, taking the target frequency domain unit as a spectrum and N1=2 as an example, the two sub-time domain resources include the first sub-time domain resource and the second sub-time domain resource. If the target CORESET is located within the two spectra, the two spectra include the first spectrum and the second spectrum. It can be that the first sub-time domain resource and the first spectrum are CORESET part 1 in the target CORESET, the first sub-time domain resource and the second spectrum are CORESET part 2 in the target CORESET, the second sub-time domain resource and the first spectrum are CORESET part 3 in the target CORESET, and the second sub-time domain resource and the second spectrum are CORESET part 4 in the target CORESET.

[0101] In some embodiments, the N1 sub-time-domain resources are determined based on the target frequency domain unit, or the N1 sub-time-domain resources are determined based on the CORESET configuration. Thus, the time-domain resources of the target CORESET can be divided into N1 sub-time-domain resources based on the target frequency domain unit, or the time-domain resources of the target CORESET can be divided into N1 sub-time-domain resources based on the CORESET configuration.

[0102] For example, taking a target frequency domain unit as a spectrum and N1=2 as an example, the two sub-time domain resources include a first sub-time domain resource and a second sub-time domain resource. If the target CORESET is located within two spectra, the two spectra include a first spectrum and a second spectrum. The first spectrum is configured with the first sub-time domain resource, and the second spectrum is configured with the second sub-time domain resource. In this case, the first sub-time domain resource and the second sub-time domain resource can be the same or different. Specifically, the size of each sub-time domain resource can be the same or different; the position of each sub-time domain resource can be the same or different.

[0103] In some embodiments, the N1 sub-time domain resources are sequentially associated with the target frequency domain unit according to the identification order of the target frequency domain unit.

[0104] For example, taking the target frequency domain unit as a spectrum and N1=3 as an example, the three sub-time domain resources include the first sub-time domain resource, the second sub-time domain resource and the third sub-time domain resource. If the target CORESET is located within the three spectra, the three spectra include the first spectrum, the second spectrum and the third spectrum. The first sub-time domain resource, the second sub-time domain resource and the third sub-time domain resource are respectively associated with the first spectrum, the second spectrum and the third spectrum.

[0105] For example, taking the target frequency domain unit as a spectrum, if the size of the time domain resource of the target CORESET is 0, it means that the corresponding spectrum has not been configured with a CORESET.

[0106] In some embodiments, the different sub-time domain resources among the N1 sub-time domain resources may have the same or different sizes, and / or, the different sub-time domain resources among the N1 sub-time domain resources do not overlap in the time domain, and / or, the size of the sub-time domain resources among the N1 sub-time domain resources is 2, 3 or K / N1, and / or, the size of each sub-time domain resource among the N1 sub-time domain resources is agreed upon by the protocol or configured by the network side.

[0107] In some embodiments, the resource indication information of the CORESET includes at least one of the following: frequency domain resource indication information, time domain resource indication information, and time-frequency domain resource indication information;

[0108] The frequency domain resource indication information is used to indicate at least one of the following:

[0109] The frequency domain resource size of the target CORESET, the frequency domain resource location of the target CORESET, the frequency domain resource size of each CORESET portion in the target CORESET, the frequency domain resource location of each CORESET portion in the target CORESET, the frequency domain resource size of each CORESET portion group in the target CORESET, and the frequency domain resource location of each CORESET portion group in the target CORESET;

[0110] The time-domain resource indication information is used to indicate at least one of the following:

[0111] The time-domain resource size of the target CORESET, the time-domain resource location of the target CORESET (e.g., OFDM symbols: 1, 2, 3, 4, 6, 7, 12, 14), the time-domain resource size of each CORESET portion in the target CORESET, the time-domain resource location of each CORESET portion in the target CORESET, the time-domain resource size of each CORESET portion group in the target CORESET, and the time-domain resource location of each CORESET portion group in the target CORESET;

[0112] The time-frequency domain resource indication information is used to indicate at least one of the following:

[0113] The time-frequency domain resource size of the target CORESET, the time-frequency domain resource location of the target CORESET, the time-frequency domain resource size of each CORESET portion in the target CORESET, the time-frequency domain resource location of each CORESET portion in the target CORESET, the time-frequency domain resource size of each CORESET portion group in the target CORESET, and the time-frequency domain resource location of each CORESET portion group in the target CORESET.

[0114] In this embodiment, the communication device can determine at least one of the following based on frequency domain resource indication information: the frequency domain resource size of the target CORESET, the frequency domain resource location of the target CORESET, the frequency domain resource size of each CORESET portion within the target CORESET, the frequency domain resource location of each CORESET portion within the target CORESET, the frequency domain resource size of each CORESET portion group within the target CORESET, and the frequency domain resource location of each CORESET portion group within the target CORESET. This allows for the expansion of the CORESET's frequency domain resources.

[0115] In this embodiment, the communication device can determine at least one of the following based on time-domain resource indication information: the time-domain resource size of the target CORESET, the time-domain resource location of the target CORESET, the time-domain resource size of each CORESET portion within the target CORESET, the time-domain resource location of each CORESET portion within the target CORESET, the time-domain resource size of each CORESET portion group within the target CORESET, and the time-domain resource location of each CORESET portion group within the target CORESET. This allows for the expansion of the CORESET's time-domain resources.

[0116] In this embodiment, the communication device can determine at least one of the following based on time-frequency domain resource indication information: the time-frequency domain resource size of the target CORESET, the time-frequency domain resource location of the target CORESET, the time-frequency domain resource size of each CORESET portion within the target CORESET, the time-frequency domain resource location of each CORESET portion within the target CORESET, the time-frequency domain resource size of each CORESET portion group within the target CORESET, and the time-frequency domain resource location of each CORESET portion group within the target CORESET. This allows for the expansion of the time-frequency domain resources of the CORESET.

[0117] In some embodiments, the target CORESET CCE satisfies at least one of the following:

[0118] The size of CCE is 6, the size of CCE is K or K*N1, the size of CCE is K / N1, the size of CCE is the size of the i-th sub-time domain resource, the size of CCE is a common multiple of the size of the i-th sub-time domain resource and 6, the size of CCE is a common multiple of K and 6, the size of CCE is determined based on the size of the target frequency domain unit, the size of CCE is determined based on the time domain resources of CORESET, the size of CCE is determined based on the frequency domain resources of CORESET, the size of CCE is determined based on a portion of CORESET, the size of CCE is determined based on a group of CORESET portions, the size of CCE is determined based on the target frequency domain unit, and the size of CCE is determined based on the sub-time domain resources of CORESET.

[0119] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, i is a positive integer, and 1≤i≤N1, and the i-th sub-temporal resource can refer to the i-th sub-temporal resource among the N1 sub-temporal resources.

[0120] For example, the target CORESET CCE is 6 in size and is compatible with the legacy NR.

[0121] For example, the size of the target CORESET CCE is K, and different CCEs occupy all the time-domain resources of the target CORESET, with the same time-domain diversity gain.

[0122] For example, the size of the target CORESET CCE is K / N1, or the size of the target CORESET CCE is the size of the i-th sub-time domain resource. The time domain resources of the target CORESET are divided into blocks for mapping, and the NR parameter can be used. The CCE sizes corresponding to different sub-time domain resources can be the same or different, and this embodiment does not limit this.

[0123] For example, the size of the target CORESET CCE is a common multiple of the size of the i-th sub-time domain resource and 6, and can be divided into N1 parts of time domain resource mapping, with the NR design used in each part of the time domain resource.

[0124] For example, the size of the target CORESET CCE is a common multiple of K and 6, and the NR parameter can be used.

[0125] For example, the size of the target CORESET CCE is determined based on CORESET parts (such as per CORESET part), and each CORESET part determines the size of the CCE separately. For example, the size of the CCE determined by different CORESET parts may be different.

[0126] For example, the size of the target CORESET CCE is determined based on CORESET part groups (e.g., per CORESET part group), and each CORESET part group determines the size of the CCE separately. For example, the size of the CCE determined by different CORESET part groups may be different.

[0127] For example, the size of the target CORESET CCE is determined based on the target frequency domain unit. Each target frequency domain unit determines the size of the CCE individually. For example, the size of the CCE determined by different target frequency domain units can be different.

[0128] For example, the size of the target CORESET CCE is determined based on the sub-temporal resources of the CORESET. The size of the CCE is determined separately for each CORESET's sub-temporal resources. For example, the size of the CCE determined by the sub-temporal resources of different CORESETs may be different.

[0129] In this embodiment, the size of the target CORESET CCE is 6, or the size of the target CORESET CCE is K or K*N1, or the size of the target CORESET CCE is K / N1, or the size of the target CORESET CCE is the size of the i-th sub-time domain resource, or the size of the target CORESET CCE is a common multiple of the size of the i-th sub-time domain resource and 6, or the size of the target CORESET CCE is a common multiple of K and 6, or the size of the target CORESET CCE is determined based on the size of the target frequency domain unit, or the size of the target CORESET CCE is determined based on the time domain resources of the CORESET, or the size of the target CORESET CCE is determined based on the frequency domain resources of the CORESET, or the size of the target CORESET CCE is determined based on a portion of the CORESET, or the size of the target CORESET CCE is determined based on a group of CORESET portions, or the size of the target CORESET CCE is determined based on the target frequency domain unit, or the size of the target CORESET CCE is determined based on the sub-time domain resources of the CORESET, thus extending the target CORESET. The size of the CCE can improve the performance of the CORESET, thereby increasing the coverage of control information in the communication system and increasing the capacity of terminals within the communication system.

[0130] The CCE mentioned in this application embodiment can be the resource scheduling unit of CORESET. One possibility is the concept of 6 REGs defined in 5G, another possibility is the concept of 9 REGs defined in LTE, yet another possibility is the concept of 1PRB corresponding to a REG with 1 symbol defined in 5G, yet another possibility is the concept of 4 REs defined in LTE, or other definitions. This application embodiment does not limit this to any other definition.

[0131] In some embodiments, the REG set of the target CORESET satisfies at least one of the following:

[0132] The REG set size is 2, the REG set size is 3, the REG set size is 6, the REG set size is K, the REG set size is K / N1, the REG set size is the size of the i-th sub-time domain resource, the REG set size is a common multiple of the size of the i-th sub-time domain resource and 6, the REG set size is a common multiple of the size of the i-th sub-time domain resource, the REG set size is a common multiple of K and 6, the REG set size is determined based on the time domain resources of the CORESET, the REG set size is determined based on the frequency domain resources of the CORESET, the REG set size is the size of the target CORESET CCE, the REG set size is agreed upon by the protocol, the REG set size is configured by the network side, the REG set size is determined based on the aggregation level, the REG set size is determined based on the CORESET portion, the REG set size is determined based on the CORESET portion group, and the REG set size is determined based on the sub-time domain resources of the CORESET.

[0133] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

[0134] The REG described in this application embodiment can be defined as: one RB in an OFDM symbol, or several resource elements (REs). For example, a REG can be composed of 9 REs.

[0135] For example, the REG set of the target CORESET can be 2, 3, or 6 in size, and can be compatible with the legacy NR.

[0136] For example, the size of the REG set of the target CORESET is K, and different REG sets occupy all the time domain resources of the target CORESET, with the same time domain diversity gain.

[0137] For example, the size of the REG set of the target CORESET is K / N1, or the size of the REG set of the target CORESET is the size of the i-th sub-time domain resource. The time domain resources of the target CORESET are divided into blocks for mapping, and the NR parameter can be used. The CCE sizes corresponding to different sub-time domain resources can be the same or different, and this embodiment does not limit this.

[0138] For example, the size of the REG set of the target CORESET is a common multiple of the size of the i-th sub-time domain resource and 6, and can be divided into N1 parts of time domain resource mapping, with the NR design used in each part of the time domain resource.

[0139] For example, the size of the REG set of the target CORESET is a common multiple of K and 6, and the NR parameter can be used.

[0140] For example, the size of the REG set of the target CORESET is the size of the CCE of the target CORESET; that is, the size of the CCE of the target CORESET can be applied to the size of the REG set of the target CORESET. For non-interleaved mappings, the size of the CCE of the target CORESET can be agreed upon by the protocol, or the size of the CCE of the target CORESET can be configured by the network side.

[0141] For example, the size of the REG bundle size for the target CORESET is determined based on the aggregation level, such as a pre-configured relationship between optional aggregation levels and REG bundle size. Aggregation level set 1 corresponds to REG bundle size L1, aggregation level set 2 corresponds to REG bundle size L2, ..., aggregation level set N corresponds to REG bundle size L N Aggregation level AL = {1, 2, 4, 8, 16} corresponds to REG bundle size L1 = 6; aggregation level AL = {1, 3, 6, 12, 24} corresponds to REG bundle size L1 = 4.

[0142] For example, the size of the REG set of the target CORESET is determined based on the CORESET part (e.g., per CORESET part), and the size of the REG set is determined separately for each CORESET part. For example, the size of the REG set determined by different CORESET parts may be different.

[0143] For example, the size of the REG set of the target CORESET is determined based on the CORESET part group (e.g., per CORESET part group), and each CORESET part group determines the size of the REG set separately. For example, the size of the REG set determined by different CORESET part groups may be different.

[0144] For example, the size of the REG set of the target CORESET is determined based on the target frequency domain unit. Each target frequency domain unit determines the size of the REG set separately. For example, the size of the REG set determined by different target frequency domain units may be different.

[0145] For example, the size of the REG set of the target CORESET is determined based on the sub-temporal resources of the CORESET. The size of the REG set is determined separately for each sub-temporal resource of the CORESET. For example, the size of the REG set of the sub-temporal resources determined for different CORESETs may be different.

[0146] In this embodiment, the size of the REG set of the target CORESET is 2, or the size of the REG set of the target CORESET is 3, or the size of the REG set of the target CORESET is 6, or the size of the REG set of the target CORESET is K, or the size of the REG set of the target CORESET is K / N1, or the size of the REG set of the target CORESET is the size of the i-th sub-time domain resource, or the size of the REG set of the target CORESET is a common multiple of the size of the i-th sub-time domain resource and 6, or the size of the REG set of the target CORESET is a common multiple of the size of the i-th sub-time domain resource, or the size of the REG set of the target CORESET is a common multiple of K and 6, or the size of the REG set of the target CORESET is determined based on the time domain resources of the CORESET, or the size of the REG set of the target CORESET is determined based on the frequency domain resources of the CORESET, or the size of the REG set of the target CORESET is the target CORESET. The size of the CCE, or the size of the REG set of the target CORESET, is determined by the protocol, configured by the network side, based on the aggregation level, based on a portion of the CORESET, based on a group of CORESET portions, or based on the sub-temporal resources of the CORESET. Expanding the size of the REG set of the target CORESET can improve the performance of the CORESET, thereby increasing the coverage of control information in the communication system and increasing the capacity of terminals within the communication system.

[0147] In some embodiments, the interleaving parameter R of the target CORESET satisfies at least one of the following:

[0148] The size of the interleaving parameter R is 2, the size of the interleaving parameter R is 3, the size of the interleaving parameter R is 6, the size of the interleaving parameter R is K, the size of the interleaving parameter R is K / N1, the size of the interleaving parameter R is the size of the i-th sub-time domain resource, the size of the interleaving parameter R is determined based on the CORESET part, the size of the interleaving parameter R is determined based on the CORESET part group, the size of the interleaving parameter R is determined based on the target frequency domain unit, and the size of the interleaving parameter R is determined based on the sub-time domain resources of the CORESET.

[0149] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

[0150] It should be noted that the size of the interleaver parameter R can represent either the interleaver rows or the interleaver columns.

[0151] For example, the interleaver size of the target CORESET can be 2, 3, or 6, which is compatible with NR legacy.

[0152] For example, the size of the interleaving parameter R of the target CORESET is determined based on the CORESET part (e.g., per CORESET part), and each CORESET part determines the size of the interleaving parameter R separately. For example, the size of the interleaving parameter R determined by different CORESET parts may be different.

[0153] For example, the size of the interleaving parameter R of the target CORESET is determined based on the CORESET part group (e.g., per CORESET part group), and each CORESET part group determines the size of the interleaving parameter R separately. For example, the size of the interleaving parameter R determined by different CORESET part groups may be different.

[0154] For example, the size of the interleaving parameter R of the target CORESET is determined based on the target frequency domain cell. Each target frequency domain cell determines the size of the interleaving parameter R separately. For example, the size of the interleaving parameter R determined by different target frequency domain cells can be different.

[0155] For example, the size of the interleaving parameter R of the target CORESET is determined based on the sub-temporal resources of the CORESET. The size of the interleaving parameter R is determined separately for each sub-temporal resource of the CORESET. For example, the size of the interleaving parameter R determined by the sub-temporal resources of different CORESETs may be different.

[0156] In some embodiments, the resource mapping information of the CORESET includes the mapping order;

[0157] The mapping order includes, but is not limited to, at least one of the following:

[0158] Time-domain resources first, then frequency-domain resources;

[0159] Frequency domain resources first, then time domain resources;

[0160] The i-th sub-time domain resource, frequency domain resource, the (i+1)-th sub-time domain resource, frequency domain resource, ..., the N1-th sub-time domain resource;

[0161] The j-th sub-frequency domain resource, time domain resource, the (j+1)-th sub-frequency domain resource, time domain resource, ..., the N2-th sub-frequency domain resource;

[0162] The i-th sub-time domain resource, the j-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, the (j+1)-th sub-frequency domain resource, ..., the N1-th sub-time domain resource, and the N2-th sub-frequency domain resource;

[0163] The j-th sub-frequency domain resource, the ith sub-time domain resource, the (j+1)-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, ..., the N2-th sub-frequency domain resource, and the N1-th sub-time domain resource;

[0164] The time-frequency domain resources of the target CORESET include N1 sub-time domain resources and N2 sub-frequency domain resources, where N1 is an integer greater than 1 and N2 is an integer greater than 1. The i-th sub-time domain resource is the i-th sub-time domain resource among the N1 sub-time domain resources, and the j-th sub-frequency domain resource is the j-th sub-time domain resource among the N2 sub-frequency domain resources.

[0165] In this embodiment, the mapping order includes, but is not limited to, at least one of the following: time-domain resources first, then frequency-domain resources; frequency-domain resources first, then time-domain resources; the i-th sub-time-domain resource, frequency-domain resource, the (i+1)-th sub-time-domain resource, frequency-domain resource, ..., the N1-th sub-time-domain resource; the j-th sub-frequency-domain resource, time-domain resource, the (j+1)-th sub-frequency-domain resource, time-domain resource, ..., the N2-th sub-frequency-domain resource; the i-th sub-time-domain resource, the j-th sub-frequency-domain resource, the (i+1)-th sub-time-domain resource, the (j+1)-th sub-frequency-domain resource, ..., the N1-th sub-time-domain resource, the N2-th sub-frequency-domain resource; the j-th sub-frequency-domain resource, the i-th sub-time-domain resource, the (j+1)-th sub-frequency-domain resource, the (i+1)-th sub-time-domain resource, ..., the N2-th sub-frequency-domain resource, the N1-th sub-time-domain resource. This allows for the expansion of the CORESET mapping order, which in turn improves the performance of the CORESET, thereby increasing the coverage of control information in the communication system and enhancing the capacity of terminals within the communication system.

[0166] For example, the mapping order includes time-domain resources first, followed by frequency-domain resources, thereby ensuring compatibility with the resource mapping order of CCE in NR.

[0167] For example, the mapping order includes frequency domain resources first, followed by time domain resources, thereby ensuring compatibility with the resource mapping order of CCE in LTE.

[0168] For example, the mapping order includes: the j-th sub-frequency domain resource, time domain resource, the (j+1)-th sub-frequency domain resource, time domain resource, ..., the N2-th sub-frequency domain resource, which is equivalent to defining CORESET part 1, CORESET part 2, ..., CORESET part N2 in the frequency domain. Subsequently, mapping can be restricted to a single CORESET part. The advantage is that if a target frequency domain unit is disabled, at least one CORESET part remains operational to transmit fallback downlink control information (DCI).

[0169] In some embodiments, the mapping order is determined based on CORESET, or the mapping order is determined based on a portion of CORESET, or the mapping order is determined based on a group of CORESET portions, or the mapping order is determined based on a target frequency domain unit, or the mapping order is determined based on sub-time domain resources.

[0170] For example, the mapping order is determined based on CORESET (e.g., per CORESET), and each CORESET determines the mapping order separately. For instance, different CORESETs may have different mapping orders.

[0171] For example, the mapping order is determined based on CORESET parts (such as per CORESET part), and each CORESET part determines the mapping order separately. For example, the mapping order determined by different CORESET parts may be different.

[0172] For example, the mapping order is determined based on CORESET part groups (e.g., per CORESET part group), and each CORESET part group determines the mapping order separately. For example, the mapping order determined by different CORESET part groups may be different.

[0173] For example, the mapping order is determined based on the target frequency domain unit, and the mapping order is determined separately for each target frequency domain unit. For instance, the mapping order determined for different target frequency domain units may be different.

[0174] For example, the mapping order is determined based on sub-time domain resources, and the mapping order is determined separately for each sub-time domain resource. For instance, the mapping order determined by the sub-time domain resources of different CORESETs may be different.

[0175] In some embodiments, the mapping order is the resource mapping order of the CCE, or the mapping order is the resource mapping order of the REG set, or the mapping order is the resource mapping order of the REG within the CCE, or the mapping order is the resource mapping order of the REG within the REG set, or the mapping order is the resource mapping order of the REG within the CORESET.

[0176] In some embodiments, the resource mapping information of CORESET includes a mapping method, and the mapping method is an interleaved mapping method;

[0177] Specifically, the time-frequency domain resources of the target CORESET are interleaved and mapped within the target frequency domain unit, or the time-frequency domain resources of the target CORESET are interleaved and mapped within the target frequency domain unit group, or the time-frequency domain resources of the target CORESET are interleaved and mapped within the CORESET portion, or the time-frequency domain resources of the target CORESET are interleaved and mapped within the CORESET portion group.

[0178] In this embodiment, the time-frequency domain resources of the target CORESET are interleaved and mapped within the target frequency domain unit, or the time-frequency domain resources of the target CORESET are interleaved and mapped within the target frequency domain unit group, or the time-frequency domain resources of the target CORESET are interleaved and mapped within a portion of the CORESET, or the time-frequency domain resources of the target CORESET are interleaved and mapped within a portion group of the CORESET. This expands the interleaving and mapping methods of the CORESET, improves the performance of the CORESET, increases the coverage of control information in the communication system, and increases the capacity of terminals in the communication system.

[0179] In some embodiments, the interleaving parameters of the interleaving mapping method satisfy at least one of the following:

[0180] The size of CCE is determined based on the target frequency domain cell, or the size of CCE is determined based on the target frequency domain cell group, or the size of CCE is determined based on CORESET;

[0181] The size L of the REG set is determined based on the target frequency domain unit, or the size L of the REG set is determined based on the target frequency domain unit group, or the size L of the REG set is determined based on CORESET.

[0182] The magnitude of the interleaving parameter R is determined based on the target frequency domain cell, or the magnitude of the interleaving parameter R is determined based on the target frequency domain cell group, or the magnitude of the interleaving parameter R is determined based on CORESET;

[0183] The interleaving parameter C is determined based on the target frequency domain cell, or the interleaving parameter C is determined based on the target frequency domain cell group, or the interleaving parameter C is determined based on CORESET;

[0184] Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units;

[0185] The resource unit is one of the following: Resource-Element Group (REG), Resource Element (RE), Physical Resource Block (PRB), or Physical Resource Group (PRG).

[0186] In this embodiment, the size of CCE is determined based on the target frequency domain unit, or the size of CCE is determined based on the target frequency domain unit group, or the size of CCE is determined based on CORESET, thereby expanding the interleaving parameters of the interleaving mapping method.

[0187] In this embodiment, the size L of the REG set is determined based on the target frequency domain unit, or the size L of the REG set is determined based on the target frequency domain unit group, or the size L of the REG set is determined based on CORESET, thereby expanding the interleaving parameters of the interleaving mapping method.

[0188] In this embodiment, the size of the interleaving parameter R is determined based on the target frequency domain unit, or the size of the interleaving parameter R is determined based on the target frequency domain unit group, or the size of the interleaving parameter R is determined based on CORESET, thereby extending the interleaving parameter R of the interleaving mapping method.

[0189] In this embodiment, the interleaving parameter C is determined based on the target frequency domain unit, or the interleaving parameter C is determined based on the target frequency domain unit group, or the interleaving parameter C is determined based on CORESET, thereby extending the interleaving parameter C of the interleaving mapping method.

[0190] In some embodiments, at least one of the following: the size of the CCE, the interleaving parameter R, the size of the REG set L, and the interleaving parameter C is applied within the target CORESET; or, at least one of the following: the size of the CCE, the interleaving parameter R, the size of the REG set L, and the interleaving parameter C is applied within the CORESET part of the target CORESET; or, at least one of the following: the size of the CCE, the interleaving parameter R, the size of the REG set L, and the interleaving parameter C is applied within the CORESET part group of the target CORESET; or, at least one of the following: the size of the CCE, the interleaving parameter R, the size of the REG set L, and the interleaving parameter C is applied within the sub-time domain resources of N1 sub-time domain resources; or, at least one of the following: the size of the CCE, the interleaving parameter R, the size of the REG set L, and the interleaving parameter C is applied within the sub-frequency domain resources of N2 sub-frequency domain resources.

[0191] In some embodiments, the time-domain resources of the target CORESET are determined based on the target frequency-domain unit, thereby expanding the time-domain resources of the target CORESET within the target frequency-domain unit.

[0192] In this embodiment, the time-domain resources of the target CORESET are determined based on the target frequency-domain units. Each target frequency-domain unit determines the time-domain resources of the target CORESET separately. For example, the time-domain resources of the target CORESET determined by different target frequency-domain units may be different.

[0193] In some embodiments, the frequency domain resources of the target CORESET are determined based on the target frequency domain cell, thereby expanding the frequency domain resources of the target CORESET within the target frequency domain cell.

[0194] In this embodiment, the frequency domain resources of the target CORESET are determined based on the target frequency domain units. Each target frequency domain unit determines the frequency domain resources of the target CORESET separately. For example, the frequency domain resources of the target CORESET determined by different target frequency domain units may be different.

[0195] In some embodiments, the size of the time-domain resources of the target CORESET is determined based on the target frequency-domain unit, thereby expanding the time-domain resources of the target CORESET within the target frequency-domain unit.

[0196] In this embodiment, the size of the time-domain resources of the target CORESET is determined based on the target frequency-domain units. Each target frequency-domain unit determines the size of the time-domain resources of the target CORESET separately. For example, the size of the time-domain resources of the target CORESET determined by different target frequency-domain units may be different.

[0197] In some embodiments, the size of the frequency domain resources of the target CORESET is determined based on the target frequency domain unit, thereby expanding the frequency domain resources of the target CORESET within the target frequency domain unit.

[0198] In this embodiment, the size of the frequency domain resources of the target CORESET is determined based on the target frequency domain units. Each target frequency domain unit determines the size of the frequency domain resources of the target CORESET separately. For example, the size of the frequency domain resources of the target CORESET determined by different target frequency domain units may be different.

[0199] In some embodiments, the frequency domain resources of the target CORESET are determined based on the priority of the target frequency domain unit, thereby expanding the frequency domain resources of the target CORESET within the target frequency domain unit.

[0200] In this embodiment, the frequency domain resources of the target CORESET are determined based on the priority of the target frequency domain units. The priority of each target frequency domain unit determines the frequency domain resources of the target CORESET separately. For example, the frequency domain resources of the target CORESET determined by the priorities of different target frequency domain units can be different.

[0201] In some embodiments, the frequency domain resources of the target CORESET are determined based on the cascading order of the target frequency domain units, thereby expanding the frequency domain resources of the target CORESET within the target frequency domain units.

[0202] In this embodiment, the frequency domain resources of the target CORESET are determined based on the cascading order of the target frequency domain units. The cascading order of each target frequency domain unit determines the frequency domain resources of the target CORESET separately. For example, the frequency domain resources of the target CORESET determined by different cascading orders of target frequency domain units can be different.

[0203] For example, taking the target frequency domain unit as a spectrum, spectrum 2, spectrum 1, and then based on the CORESET bitmap, from the lowest PRB of spectrum 2 to the PRB resource mapping of spectrum 1, the resources of the target CORESET are determined.

[0204] In some embodiments, the size of the CORESET portion in the target CORESET is determined based on the target frequency domain unit, thereby expanding the frequency domain resources of the CORESET portion in the target CORESET within the target frequency domain unit.

[0205] In this embodiment, the size of the CORESET portion in the target CORESET is determined based on the target frequency domain unit. Each target frequency domain unit individually determines the size of the CORESET portion in the target CORESET. For example, the size of the CORESET portion in the target CORESET determined by different target frequency domain units may be different.

[0206] For example, taking the target frequency domain unit as a spectrum, the frequency domain resources of CORESET part 1 and CORESET part 2 are determined proportionally based on the size of spectrum 1 and the size of spectrum 2.

[0207] In some embodiments, the size of the CORESET portion group in the target CORESET is determined based on the target frequency domain unit, thereby expanding the frequency domain resources of the CORESET portion group in the target CORESET within the target frequency domain unit.

[0208] In this embodiment, the size of the CORESET portion group in the target CORESET is determined based on the target frequency domain unit. Each target frequency domain unit determines the size of the CORESET portion group in the target CORESET separately. For example, the size of the CORESET portion group in the target CORESET determined by different target frequency domain units may be different.

[0209] In some embodiments, the resource indication information of the CORESET can be carried by the PDCCH, or the resource indication information of the CORESET can be carried by the Media Access Control Control Element (MAC CE), or the resource indication information of the CORESET can be carried by higher-layer signaling.

[0210] In some embodiments, the frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit.

[0211] In this embodiment, the frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit, so that the target CORESET can be applied to the target frequency domain unit.

[0212] In some embodiments, the resources of the target CORESET are the intersection of the resources of the CORESET determined based on the resource indication information of the CORESET and the resources of the target frequency domain unit.

[0213] In this embodiment, the resources (time-frequency resources) of the target CORESET are the intersection of the resources (time-frequency resources) of the CORESET determined based on the resource indication information of the CORESET and the resources (time-frequency resources) of the target frequency domain unit, so that the target CORESET can be applied to the target frequency domain unit.

[0214] In some embodiments, the frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit, and the interleaving parameter C corresponding to the frequency domain resources of the target CORESET is an integer.

[0215] In this embodiment, the frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit. The interleaving parameter C corresponding to the frequency domain resources of the target CORESET is an integer, so it can be applied to the interleaving mapping method, and the target CORESET can be applied to the target frequency domain unit.

[0216] In some embodiments, the frequency domain resources indicated by the resource indication information of CORESET start from PRB 0 of the target frequency domain unit.

[0217] In some embodiments, if the number of target frequency domain units in which the target CORESET is located is greater than or equal to 2 (i.e., at least two target frequency domain units), the frequency domain resources indicated by the resource indication information of the CORESET start from the minimum PRB of at least two target frequency domain units.

[0218] For example, taking the target frequency domain unit as a spectrum, the frequency domain resources indicated by the resource indication information of CORESET start from the minimum PRB of at least two spectra. If spectrum 1 PRB H1~PRB H2, spectrum 2 PRB F1~PRB F2, then the range of spectra is min(H1,F1)~max(H2,F2).

[0219] In some embodiments, if the number of target frequency domain units in which the target CORESET is located is greater than or equal to 2 (i.e., at least two target frequency domain units), the frequency domain resources indicated by the resource indication information of the CORESET are respectively based on the minimum PRB of each target frequency domain unit.

[0220] In some embodiments, the size of the resource indication information of the CORESET is determined based on at least one of the following: the frequency domain resource indication granularity of the target CORESET, the number of OFDM symbols occupied by the target CORESET, the target frequency domain cell in which the target CORESET is located, the range of the minimum and maximum PRBs of the target frequency domain cell in which the target CORESET is located, the total number of PRBs in the target frequency domain cell in which the target CORESET is located, and the relationship between the frequency domain resource indication granularity of the target CORESET and the target frequency domain cell.

[0221] For example, the size of the resource indication information of CORESET is determined based on the range of the minimum and maximum PRBs of the target frequency domain unit where the target CORESET is located. Taking the target frequency domain unit as a spectrum as an example, such as spectrum 1 PRB H1~PRB H2, spectrum 2 PRB F1~PRB F2, then the range of the minimum and maximum PRBs of the spectrums is min(H1,F1)~max(H2,F2).

[0222] For example, the size of the resource indication information of CORESET is determined based on the total number of PRBs in the target frequency domain unit where the target CORESET is located. Taking the target frequency domain unit as a spectrum as an example, spectrum 1 PRB H1~PRB H2, spectrum 2 PRB F1~PRB F2, then the total number of PRBs in the spectrums is (H2-H1)+(F2-F1).

[0223] For example, the size of the resource indication information for a CORESET is determined based on the relationship between the frequency domain resource indication granularity of the target CORESET and the target frequency domain unit. Taking the target frequency domain unit as a spectrum as an example, for spectrum 1 PRB H1~PRB H2, spectrum 2 PRB F1~PRB F2, the size of the resource indication information for the CORESET is ceil((H2-H1) / K)+ceil((F2-F1) / K). ceil() rounds up, meaning that if the last K PRBs are less than K, 1 bit is used to indicate whether it is a resource of the target CORESET. Alternatively, for spectrum 1 PRB H1~PRB H2, spectrum 2 PRB F1~PRB F2, the size of the resource indication information for the CORESET is floor((H2-H1) / K)+floor((F2-F1) / K). floor() rounds down, meaning that if the last K PRBs are less than K, they are not indicated, and by default, they are not within the resources of the target CORESET.

[0224] In some embodiments, the frequency domain resource indication granularity of the target CORESET is M PRBs, where the M PRBs are either contiguous resources or non-contiguous resources, and M is a positive integer. Optionally, the M PRBs are resources spanning multiple target frequency domain units. Compared to allowing M PRBs to be non-contiguous, this approach only allows non-contiguous resources between target frequency domain units, limiting the application scenarios of non-contiguous M PRBs.

[0225] In some embodiments, the frequency domain resource indication granularity of the target CORESET is determined based on the target frequency domain cells, or the frequency domain resource indication granularity of the target CORESET is determined based on the number of OFDM symbols occupied by the target CORESET.

[0226] For example, the frequency domain resource indication granularity of the target CORESET is 1 PRB, 2 PRB, 3 PRB, 6 PRB, or 12 PRB.

[0227] For example, the frequency domain resource indication granularity of the target CORESET is determined based on the target frequency domain cells. Each target frequency domain cell individually determines the frequency domain resource indication granularity of the target CORESET. For example, the frequency domain resource indication granularity of the target CORESET determined by different target frequency domain cells may be different.

[0228] For example, the frequency domain resource indication granularity of the target CORESET is determined based on the number of OFDM symbols occupied by the target CORESET, keeping the CCE unchanged, and the frequency domain granularity is related to the time domain granularity. For instance, when the number of OFDM symbols occupied by the target CORESET is 2, the frequency domain of the target CORESET is indicated with a granularity of 3 PRBs; when the time domain has 3 symbols, the frequency domain is indicated with a granularity of 2 PRBs.

[0229] In some embodiments, the aggregation level of the CORESET includes, but is not limited to, at least one of the following: 1, 2, 3, 4, 5, 6, 7, 8, 16, 32, 64, 128.

[0230] In some embodiments, the aggregation level of the CORESET is determined based on the size of the REG set, or the aggregation level of the CORESET is determined based on the number of OFDM symbols occupied by the target CORESET.

[0231] For example, if the REG bundle size is 2, 3, or 6, then the possible aggregation levels AL are {1, 2, 4, 8, 16}; if the REG bundle size is 4 or 8, then the possible aggregation levels AL are {1, 3, 6, 12, 24}.

[0232] In some embodiments, the aggregation level of the CORESET is determined based on the CORESET (per CORESET). For example, an aggregation level can be configured within a single CORESET.

[0233] For example, the aggregation level of a CORESET is determined based on the CORESET. Each CORESET has its own aggregation level, and for example, the aggregation levels of different CORESETs may be different.

[0234] In some embodiments, the aggregation level of the CORESET is determined based on a CORESET part. For example, the aggregation level can be configured in a CORESET part, and if there are two CORESET parts, then the aggregation level will be configured in each CORESET part.

[0235] For example, the aggregation level of a CORESET is determined based on a CORESET part, and each CORESET part determines the aggregation level of the CORESET separately. For instance, the aggregation level of a CORESET determined by different CORESET parts may be different.

[0236] In some embodiments, the aggregation level of the CORESET is determined based on a CORESET subset group.

[0237] For example, the aggregation level of a CORESET is determined based on a CORESET part group. Each CORESET part group determines the aggregation level of a CORESET separately. For instance, the aggregation levels of CORESETs determined by different CORESET part groups may be different.

[0238] In some embodiments, the aggregation level of the CORESET is determined based on the target frequency domain unit.

[0239] For example, the aggregation level of CORESET is determined based on the target frequency domain unit. Each target frequency domain unit determines the aggregation level of CORESET separately. For instance, the aggregation level of CORESET determined by different target frequency domain units may be different.

[0240] In some embodiments, the aggregation level of CORESET is determined based on sub-temporal resources.

[0241] For example, the aggregation level of CORESET is determined based on sub-time domain resources. Each sub-time domain resource determines the aggregation level of CORESET separately. For instance, the aggregation level of CORESET determined by different sub-time domain resources may be different.

[0242] In some embodiments, the terminal capabilities include, but are not limited to, at least one of the following:

[0243] The terminal supports precoding based on the target frequency domain unit, or the terminal supports precoding based on the CORESET portion, or the terminal supports precoding based on the CORESET portion group;

[0244] The terminal supports REG set sizes of 2, 3, 6, K, K / N1, the size of the i-th sub-time domain resource, a common multiple of the size of the i-th sub-time domain resource and 6, a common multiple of the size of the i-th sub-time domain resource, a common multiple of K and 6, a size determined based on the time domain resources of the CORESET, a size determined based on the frequency domain resources of the CORESET, a size equal to the size of the CCE corresponding to the target CORESET, or a size agreed upon by the protocol. The size of the REG set can be configured by the network side, determined based on the aggregation level, determined based on the CORESET portion, determined based on the CORESET portion group, or determined based on the sub-temporal resources of the CORESET; wherein, the temporal resource size of the target CORESET is K, and the temporal resources of the target CORESET include N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1;

[0245] The terminal supports 4, 5, 6, 7, 8, 12, or 14 OFDM symbols for CORESET time-domain resources, or the terminal supports one time slot for CORESET time-domain resources.

[0246] The terminal supports repeated transmission of CORESET;

[0247] The terminal supports the target frequency domain unit;

[0248] The terminal supports bandwidth of X MHz or X PRBs, and / or the terminal supports bandwidth of less than X MHz or X PRBs, where X is a non-negative number, and X is determined by the protocol or configured by the network side.

[0249] The terminal supports NTN services;

[0250] Does the terminal's CORESET support at least two carriers or at least two target frequency domain units, or does the terminal's CORESET support non-contiguous spectrum resources?

[0251] For example, X is less than 25 PRBs.

[0252] In some embodiments, the number of PDCCH candidates within the target CORESET is determined based on at least one of the following:

[0253] The aggregation level of the CORESET;

[0254] The number of CCEs within the CORESET section;

[0255] Number of resource units within the CORESET section;

[0256] The number of CCEs within the CORESET section;

[0257] Number of resource units within a CORESET group;

[0258] The number of CCEs within the target frequency domain cell;

[0259] The number of resource units within the target frequency domain unit;

[0260] The number of CCEs within the target frequency domain cell group;

[0261] The number of resource units within the target frequency domain unit group;

[0262] Number of CCEs within a sub-time domain unit;

[0263] The number of resource units within a sub-time domain unit;

[0264] The resource unit is one of the following: REG, RE, PRB, PRG.

[0265] For example, the number of PDCCH candidates within a target CORESET is determined based on the CORESET's aggregation level. For aggregation levels AL = 3, 5, 6, 7, 32, 64, 128, the number of selectable PDCCH candidates is {0, 1, 2, 3, 4, 5, 6, 7, 8}. NR configures the number of PDCCH candidates per AL. The key difference here is the introduction of parameters like AL ​​= 3, which changes the number of PDCCH candidates.

[0266] For example, the PDCCH candidate within the target CORESET is determined within the target CORESET.

[0267] For example, the PDCCH candidate within the target CORESET is determined within the CORESET part of the target CORESET. For instance, the PDCCH candidate is determined based on the number of CCEs / resource units within the CORESET part (that is, limiting PDCCH reception to within the CORESET part, which is similar to configuring a smaller CORESET).

[0268] For example, the PDCCH candidate within the target CORESET is determined within the CORESET part group. For instance, the PDCCH candidate is determined based on the number of CCEs / resource units within the CORESET part group (i.e., limiting PDCCH reception to within the CORESET part group, which is similar to configuring a smaller CORESET).

[0269] For example, the PDCCH candidate within the target CORESET is determined within the target frequency domain cell or target frequency domain cell group. For instance, taking the target frequency domain cell as a spectrum, the PDCCH candidate is determined based on the number of CCE / resource cells within the spectrum (group).

[0270] For example, the PDCCH candidate within the target CORESET is determined within the time-domain resource group of the target CORESET. For instance, the PDCCH candidate is determined based on the number of CCEs / resource units within the time-domain resource group of the target CORESET.

[0271] In some embodiments, the resources of the target frequency domain unit corresponding to the target CORESET are determined based on at least one of the following: Quality of Service (QoS), aggregation level, and terminal capabilities.

[0272] For example, QoS can be transmission rate, priority, latency, throughput, etc.

[0273] In some embodiments, the precoder corresponding to the target CORESET is determined based on the CORESET (per CORESET).

[0274] For example, the precoding corresponding to the target CORESET is determined based on the CORESET. Each CORESET individually determines the precoding corresponding to the target CORESET. For instance, the precoding corresponding to the target CORESET determined by different CORESETs can be different.

[0275] In some embodiments, the precoding corresponding to the target CORESET is determined based on the CORESET part.

[0276] For example, the precoding corresponding to the target CORESET is determined based on the CORESET part. Each CORESET part determines the precoding corresponding to the target CORESET separately. For example, the precoding corresponding to the target CORESET determined by different CORESET parts can be different.

[0277] In some embodiments, the precoding corresponding to the target CORESET is determined based on the CORESET part group.

[0278] For example, the precoding corresponding to the target CORESET is determined based on the CORESET part group. Each CORESET part group determines the precoding corresponding to the target CORESET separately. For example, the precoding corresponding to the target CORESET determined by different CORESET part groups can be different.

[0279] In some embodiments, the precoding corresponding to the target CORESET is determined based on the target frequency domain unit.

[0280] For example, the precoding corresponding to the target CORESET is determined based on the target frequency domain unit. Each target frequency domain unit independently determines the precoding corresponding to the target CORESET. For example, the precoding corresponding to the target CORESET determined by different target frequency domain units can be different.

[0281] In some embodiments, the precoding corresponding to the target CORESET is determined based on sub-temporal units.

[0282] For example, the precoding corresponding to the target CORESET is determined based on sub-time domain units. Each sub-time domain unit determines the precoding corresponding to the target CORESET separately. For example, the precoding corresponding to the target CORESET determined by different sub-time domain units can be different.

[0283] In some embodiments, the first information is determined based on at least one of the following:

[0284] Subcarrier spacing (SCS), Cyclic prefix (CP).

[0285] For example, the first piece of information is determined based on the SCS. Taking the target frequency domain unit as a spectrum as an example, when different spectra are configured with different SCS, parameter configuration per spectrum is required. However, in this case, two CORESETs are usually configured.

[0286] For example, the first piece of information is determined based on the CP. Taking the target frequency domain unit as a spectrum as an example, when different spectra are configured with different CPs, parameter configuration per spectrum is required. However, in this case, two CORESETs are usually configured.

[0287] In some embodiments, if the target CORESET is CORESET 0, or the target CORESET is the CORESET of the target frequency domain unit for initial access, or the target CORESET is the CORESET of the System Information Block (SIB) (such as SIB 1), the time-frequency domain resources of the target CORESET are defined by the protocol, and / or the size of the target CORESET CCE is defined by the protocol, and / or the size of the REG set of the target CORESET is defined by the protocol, and / or the size of the interleaving parameter R of the target CORESET is defined by the protocol, and / or the aggregation level corresponding to the target CORESET is defined by the protocol.

[0288] In some embodiments, the transmission of the PDCCH within the target CORESET satisfies at least one of the following:

[0289] The transmission of PDCCH in CORESET part P is a repetition of the transmission of PDCCH in CORESET part Q;

[0290] The transmission of PDCCH in the CORESET portion of the target frequency domain unit P is a repetition of the transmission of PDCCH in the CORESET portion of the target frequency domain unit Q;

[0291] The transmission of PDCCH within the CORESET portion of time-domain resource set P is a repetition of the transmission of PDCCH within the CORESET portion of time-domain resource set Q;

[0292] Where P and Q are both integers greater than or equal to 0.

[0293] In this embodiment, the PDCCH within the target CORESET supports repeated transmission in different CORESET parts, and / or, the PDCCH within the target CORESET supports repeated transmission in different target frequency domain units, and / or, the PDCCH within the target CORESET supports repeated transmission in different time domain resource sets.

[0294] It should be noted that, in the embodiments of this application, for schemes that map to only one target frequency domain unit, the changes are basically limited to updating configuration parameters and triggering conditions, with minor modifications to NR. For OFDM symbols > 3, the current CORESET resource mapping scheme is the more innovative part of this scheme. Taking the target frequency domain unit as a spectrum as an example, the scheme of CORESET within one spectrum can be applied to scenarios where CORESET occupies multiple spectra.

[0295] Therefore, in this embodiment of the application, the communication device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information (at least one of the resource information of the target frequency domain unit, the resource indication information of the CORESET, the resource mapping information of the CORESET, the aggregation level of the CORESET, the terminal capability, the frequency domain range, and the service type). This can expand the resources of the CORESET (such as expanding the resources of the CORESET within the target frequency domain unit), and / or expand the frequency domain resource indication granularity of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET, thereby improving the performance of the CORESET, increasing the coverage of control information in the communication system, and increasing the capacity of terminals in the communication system.

[0296] The technical solution of this application is described in detail below through specific embodiments.

[0297] It should be noted that in the following embodiments, the value of offset (n_shift) can be agreed upon by the protocol, or the value of offset (n_shift) can be pre-configured by the network side, or the value of offset (n_shift) can be dynamically configured by the network side. Specifically, for example, offset (n_shift) is a value greater than 0 and / or equal to 0.

[0298] Example 1, taking the time-domain extended CORESET resources as an example, defines a CORESET of 4 OFDM symbols (OS), meaning the target CORESET occupies 4 OSs in the time domain, with REG bundle size L=2 or REG bundle size L=6. This solves the problem of insufficient control resources and achieves gains in improving control channel performance and / or improving network downlink coverage.

[0299] Scheme 1-1, target CORESET of 4 OFDM symbols; CCE = 6 REGs, REG bundle size L = 6.

[0300] The temporal resources of the target CORESET include a first sub-temporal resource and a second sub-temporal resource (i.e., N1 = 2 above), wherein the first sub-temporal resource is symbol 0 and symbol 1; and the second sub-temporal resource is symbol 2 and symbol 3.

[0301] Specifically, mapping is performed on a CCE or REG bundle basis, following the order of first sub-time domain resources, then frequency domain resources, and finally the second sub-time domain resources. Within a CCE or a REG bundle, REGs are mapped in the order of first time domain resources, then frequency domain resources.

[0302] If a non-interleaved method is used, taking CCE as the unit as an example, one mapping method can be shown in Figure 5.

[0303] It should be noted that CCE in Figure 5 can also be replaced with REG bundle (i.e., in units of REG bundles), but for the sake of brevity, this will not be elaborated further here.

[0304] Scheme 1-2, target CORESET of 4 OFDM symbols; CCE = 6 REGs, REG bundle size L = 6.

[0305] The temporal resources of the target CORESET include a first sub-temporal resource and a second sub-temporal resource (i.e., N1 = 2 above), wherein the first sub-temporal resource is symbol 0 and symbol 1; and the second sub-temporal resource is symbol 2 and symbol 3.

[0306] Specifically, using CCE or REG bundles as units, mapping is performed first for time-domain resources (or first for the first sub-time-domain resource, then for the second sub-time-domain resource), followed by frequency-domain resources. Within a CCE or a REG bundle, REGs are mapped in the order of first sub-time-domain resources, second sub-time-domain resources, and then frequency-domain resources.

[0307] If a non-interleaved method is used, taking CCE as the unit as an example, one mapping method can be shown in Figure 6.

[0308] It should be noted that CCE in Figure 6 can also be replaced with REG bundle (i.e., in units of REG bundles), but for the sake of brevity, this will not be elaborated further here.

[0309] Scheme 1-3, target CORESET of 4 OFDM symbols; CCE = 6 REGs, REG bundle size L = 6.

[0310] Specifically, mapping is performed on a CCE or REG bundle basis, prioritizing time-domain resources before frequency-domain resources. Within a CCE or a REG bundle, REG resources are mapped in the order of time-domain resources first, followed by frequency-domain resources.

[0311] If a non-interleaved method is used, taking CCE as the unit as an example, one mapping method can be shown in Figure 7.

[0312] It should be noted that CCE in Figure 7 can also be replaced with REG bundle (i.e., in units of REG bundles), but for the sake of brevity, this will not be elaborated further here.

[0313] Scheme 1-4, target CORESET of 4 OFDM symbols; CCE = 6 REGs, REG bundle size L = 2.

[0314] The temporal resources of the target CORESET include a first sub-temporal resource and a second sub-temporal resource (i.e., N1 = 2 above), wherein the first sub-temporal resource is symbol 0 and symbol 1; and the second sub-temporal resource is symbol 2 and symbol 3.

[0315] Specifically, the mapping is performed on a REG bundle basis, following the order of first sub-time domain resources, then frequency domain resources, then second sub-time domain resources, and finally frequency domain resources. Within a REG bundle, the REGs are mapped in the order of first sub-time domain resources, then second sub-time domain resources, and finally frequency domain resources.

[0316] If interleaving is used, when the interleaving parameter R is 3, then C = Nreg / (LR) = 36 / (2*3) = 6, and the offset (n_shift) = 0. One mapping method is shown in Figure 8, where B0 represents REG bundle 0, and so on.

[0317] Scheme 1-5, target CORESET of 4 OFDM symbols; CCE=6 REG, REG bundle size L=2.

[0318] The temporal resources of the target CORESET include a first sub-temporal resource and a second sub-temporal resource (i.e., N1 = 2 above), wherein the first sub-temporal resource is symbol 0 and symbol 1; and the second sub-temporal resource is symbol 2 and symbol 3.

[0319] Specifically, taking REG bundles as units, time-domain resources (or first sub-time-domain resources followed by the second sub-time-domain resources) are mapped first, followed by frequency-domain resources. Within a REG bundle, REGs are mapped in the order of first sub-time-domain resources, second sub-time-domain resources, and then frequency-domain resources.

[0320] If interleaving is used, and the interleaving parameter R is 3, then C = Nreg / (LR) = 36 / (2*3) = 6, and the offset (n_shift) = 0. One mapping method is shown in Figure 9, where B0 represents REG bundle 0, and so on.

[0321] It should be noted that, compared with Scheme 1-4, the time-domain hierarchical gain of a single CCE in Scheme 1-5 is worse than the time-domain diversity gain of a single CCE in Scheme 1-4.

[0322] Scheme 1-6, target CORESET of 4 OFDM symbols; CCE = 6 REGs, REG bundle size L = 2.

[0323] Specifically, the mapping is performed on a REG bundle basis, prioritizing time-domain resources before frequency-domain resources. Within a single REG bundle, REGs are mapped in the order of time-domain resources first, followed by frequency-domain resources.

[0324] If interleaving is used, when the interleaving parameter R is 3, then C = Nreg / (LR) = 36 / (2*3) = 6, and the offset (n_shift) = 0. One mapping method is shown in Figure 9, where B0 represents REG bundle 0, and so on.

[0325] Example 2, taking the time-domain extended CORESET resources as an example, defines a 4 OFDM symbol (OS) CORESET, meaning the target CORESET occupies 4 OS in the time domain, with REG bundle size L = 4 or REG bundle size L = 8. This matches the time-domain symbol count of the CORESET, increases the control resource size, and achieves gains in improving control channel performance and / or network downlink coverage, while reducing UE processing complexity. However, this approach requires more protocol modifications.

[0326] Scheme 2-1, 4 OFDM symbols target CORESET; CCE = 4 REGs, REG bundle size L = 4.

[0327] A non-interleaved mapping method can be shown in Figure 10, which adopts a mapping method that prioritizes time-domain resources over frequency-domain resources.

[0328] Scheme 2-2, 4 OFDM symbol target CORESET; CCE = 8 REGs, REG bundle size L = 8.

[0329] A non-interleaved mapping method can be achieved by using a mapping approach that prioritizes time-domain resources over frequency-domain resources, as shown in Figure 11.

[0330] Scheme 2-3, 4 OFDM symbol target CORESET; CCE = 4 REGs, REG bundle size L = 4.

[0331] A mapping method is adopted that prioritizes time-domain resources over frequency-domain resources.

[0332] If interleaving is used, the size of the interleaving parameter R is 4, C = Nreg / (LR) = 32 / (4*4) = 2, and the offset (n_shift) = 0. One interleaving mapping method can be shown in Figure 12.

[0333] Scheme 2-4, 4 OFDM symbols target CORESET; CCE = 8 REGs, REG bundle size L = 4.

[0334] A mapping method is adopted that prioritizes time-domain resources over frequency-domain resources.

[0335] If interleaving is used, the size of the interleaving parameter R is 4, C = Nreg / (LR) = 32 / (4*4) = 2, and the offset (n_shift) = 0. One interleaving mapping method can be shown in Figure 13. In Figure 13, B0 represents REG bundle 0, and so on.

[0336] Example 3, taking the expansion of the aggregation level of the target CORESET and the target frequency domain unit as a spectrum as an example, allows for flexible configuration of the aggregation level within a CORESET, expanding the available PRB resources under low bandwidth conditions. This solves the problem of insufficient frequency domain resources within a single spectrum leading to limited coverage or a limited number of UE access points, achieving gains in increased coverage and / or increased UE capacity.

[0337] It should be noted that the configurable aggregation levels in NR are {1,2,4,8,16}.

[0338] Solution 3-1, the set of optional parameters of the aggregation level (AL) is a subset or the whole set of {1, 2, 3, 4, …, 7, 8, 16, 32, 64, 128}.

[0339] AL = 3, the frequency-domain resources of the target CORESET are 6 PRBs, and the mapping starts from the starting position of the spectrum.

[0340] If the resource mapping method of the target CORESET is a non-interleaved mapping method (the abscissa is PRB and the ordinate is symbol), as shown in Figure 14.

[0341] If the resource mapping method of the target CORESET is an interleaved mapping method, one interleaved mapping parameter is: L = 3, R = 2, offset (n_shift) = 0, as shown in Figure 15.

[0342] Solution 3-2, the optional parameters of the aggregation level are determined according to the bandwidth.

[0343] When the bandwidth < W1, the set of optional parameters is AL = {1, 2, 3, 4, …, 7}.

[0344] When the bandwidth > W2, the set of optional parameters is AL = {1, 2, 4, 8, 16, 32, 64, etc.}.

[0345] When W1 <= bandwidth <= W2, the set of optional parameters is {1, 2, 4, 8, 16}.

[0346] Among them, W1 and W2 are predefined / configured parameters. Optionally, the units of W1 and W2 are PRBs or MHz. For example: W1 = 11 PRBs (30 kHz, 5 MHz bandwidth), or 25 PRBs.

[0347] Predefine W1 = 25 PRBs. Configure the bandwidth of the spectrum to be 11 PRBs, and 11 PRBs < 25 PRBs. So the configurable AL = {1, 2, 3, 4, …, 7}.

[0348] Configure the AL of the target CORESET to be 3 and adopt non-interleaved mapping, as shown in Figure 14.

[0349] Alternatively, configure the AL of the target CORESET to be 3 and adopt interleaved mapping, and the interleaved mapping parameters are L = 3, R = 2, n_shift = 0, as shown in Figure 15.

[0350] It should be noted that "=" can also be bandwidth <= W1, or bandwidth >= W2, or W1 < bandwidth < W2, or W1 <= bandwidth < W2, or W1 < bandwidth <= W2.

[0351] Solution 3-3. The optional parameter of the aggregation level is determined according to the DCI size.

[0352] When the DCI size <= size 1, the optional aggregation level is Set 1;

[0353] When size 1 < DCI size < size 2, the optional aggregation level is Set 2;

[0354] When the DCI size >= size 2, the optional aggregation level is Set 3.

[0355] It should be noted that "=" can also be size 1 <= DCI size <= size 2, or size 1 <= DCI size < size 2, or size 1 < DCI size <= size 2.

[0356] It should be noted that the DCI size and the resources are independently configured, so that the code rate can be any combination. If the aggregation level AL is bound to the DCI size, the code rate ranges that different DCIs can obtain are basically the same. There will be no overly large or overly small code rates. However, the flexibility is lower.

[0357] Embodiment 4. Taking the expansion of the frequency-domain configuration granularity and the target frequency-domain unit as spectrum as an example, the frequency-domain resources within a CORESET can be not an integer multiple of 6 PRB groups. Thus, the problem that the frequency-domain resources within a single spectrum are insufficient, resulting in limited coverage or limited number of UE accesses, is solved, and the gain of improving the coverage and / or improving the UE capacity is achieved. Here, the configuration granularity of the frequency domain can also be determined according to the time-domain resources of the CORESET or the time-domain resources of the CORESET part. Some specific possible configurations are: if the time-domain resources are 2 OS, the frequency-domain resource configuration granularity is 3 PRBs; if the time-domain resources are 3 OS, the frequency-domain resource configuration granularity is 2 PRBs. Configuring the frequency-domain resources according to the time-domain resources can make the interleaving parameter C an integer when using interleaved mapping.

[0358] It should be noted that in NR, the frequency-domain configuration of the CORESET is indicated by a 45-bit bitmap, and each 1 bit represents 6 PRB groups.

[0359] Solution 4-1. The frequency-domain configuration granularity of the CORESET is 1, 2, 3, 6 PRB(s).

[0360] When the spectrum bandwidth is 11 PRBs, the frequency-domain configuration granularity is 3 PRBs, and the target CORESET CCE can be as shown in Figure 16.

[0361] If the frequency-domain configuration granularity is 2 PRBs, when the spectrum bandwidth is 11 PRBs, the target CORESET CCE can be as shown in Figure 17.

[0362] Solution 4-2, the frequency-domain configuration granularity of the CORESET is determined according to the bandwidth.

[0363] When the bandwidth < S1, the frequency-domain configuration granularity is 3 PRBs, or the frequency-domain configuration granularity is 2 PRBs.

[0364] When the bandwidth > S1, the frequency-domain configuration granularity is 6 PRBs.

[0365] Among them, S1 is a predefined / configured parameter. Optionally, the unit of S1 is PRBs or MHz. For example: S1 = 11 PRBs (30 kHz, 5 MHz bandwidth), or 25 PRBs.

[0366] Predefine S1 = 25 PRBs. Configure the bandwidth of the Spectrum to be 11 PRBs, 11 PRBs < 25 PRBs. So the frequency-domain configuration granularity is 3 PRBs (as shown in Figure 16), or the frequency-domain configuration granularity is 2 PRBs (as shown in Figure 17).

[0367] Embodiment 5, taking the target frequency-domain unit as the spectrum and the intersection of the indicated / configured target CORESET resources and the spectrum resources as an example, the frequency-domain resources within a CORESET can be non-integer multiples of 6 PRB groups, and at the same time, the available frequency-domain resources can be maximized. Thus, the problem of limited coverage or limited number of UE accesses caused by insufficient frequency-domain resources within a single spectrum is solved, and the gain of improving the coverage range and / or improving the UE capacity is achieved.

[0368] It should be noted that in NR, the frequency-domain configuration of the CORESET is indicated by a 45-bit bitmap, and each 1 bit (bit) represents 6 PRB groups.

[0369] Solution 5-1, if the configured target CORESET resources are 12 PRBs and the frequency-domain resource size of the spectrum is 11 PRBs; define the resources of the target CORESET as the intersection of the configured target CORESET resources and the spectrum, then the resources of the target CORESET are PRB 0 to PRB 10.

[0370] Optionally, the target CORESET CCE is mapped starting from the lowest PRB of the CORESET or starting from the highest PRB of the CORESET.

[0371] If mapping starts from the lowest PRB in the CORESET, and the REG bundle size L = 6 REGs, a non-interleaved mapping method for the resources of a target CORESET can be shown in Figure 18.

[0372] Scheme 5-2: If the configured target CORESET resource size is 12 PRBs and the spectrum frequency domain resource size is 11 PRBs; define the target CORESET resource as the intersection of the configured target CORESET resource and the spectrum, then the target CORESET resource size is PRB 0 to PRB 10. The number of REGs within the target CORESET, Nreg = 33.

[0373] If the resources of the target CORESET use interleaved mapping, one interleaved mapping parameter configuration is as follows: REG bundle size L = 3 REGs, interleaved parameter R size = 2, C = floor(Nreg / (LR)) = 5 (here, the value of C is taken as floor(x) as an example, it can also be rounded to the nearest integer or rounded up), as shown in Figure 19.

[0374] Scheme 5-3: If the configured target CORESET resource size is 12 PRBs and the spectrum frequency domain resource size is 11 PRBs; define the target CORESET resource as the intersection of the configured target CORESET resource and the spectrum, such that C is an integer, then the target CORESET resource size is PRB 0 to PRB 9 (wherein, the target CORESET frequency domain resource can be continuous or non-contiguous frequency domain sources). The number of REGs within the target CORESET, Nreg = 30.

[0375] If the resources of the target CORESET use interleaved mapping, one interleaved mapping parameter configuration is as follows: REG bundle size L = 3 REGs, interleaved parameter R size = 2, C = Nreg / (LR) = 5, as shown in Figure 20.

[0376] Example 6, taking a target frequency domain unit as a spectrum and multiple spectra with the same time domain size as an example, shows that the target CORESET occupies two spectra, and the time domain resource size and location are the same on both spectra. This solves the problem of insufficient frequency domain resources within a single spectrum leading to limited coverage or a limited number of UEs, achieving gains in improving coverage and / or increasing UE capacity.

[0377] Scheme 6-1, interleaving is performed within the per spectrum.

[0378] The target CORESET can be configured to interleaving as per spectrum or per CORESET part, or interleaving as per CORESET.

[0379] The target CORESET occupies CORESET part 1 resources on spectrum 1, and the target CORESET occupies CORESET part 2 resources on spectrum 2.

[0380] If the network side is configured to interleaving the target CORESET as per spectrum, per spectrum group, per CORESET part, or per CORESET part group.

[0381] The target CORESET is interleaved within the spectrum / CORESET part.

[0382] Optionally, the CCE size (Nreg) can be configured per spectrum or per spectrum group, or the CCE size (Nreg) can be configured per CORESET.

[0383] Optionally, REG bundle size L can be configured per spectrum or per spectrum group, or REG bundle size L can be configured per CORESET.

[0384] Optionally, the size of the interleaver parameter R can be configured per spectrum or per spectrum group, or per CORESET.

[0385] Optionally, the interleaving parameter C is calculated per spectrum or per spectrum group, or the interleaving parameter C is calculated per CORESET.

[0386] Where C = Nreg_1 / (LR), or C = floor(Nreg_1 / (LR)), or C = ceil(Nreg_1 / (LR)), or C = round(Nreg_1 / (LR)).

[0387] Nreg_1 is one of the following:

[0388] CORESET's CCE size = Nreg (as shown in Figure 21, C = 9);

[0389] The CCE size of CORESET part 1 (group) (as shown in Figure 21, C1 = 3);

[0390] The CCE size of CORESET part 2 (group) (as shown in Figure 21, C2 = 6).

[0391] It should be noted that for CCE size, REG bundle size L and R are configurable parameters, which can be configured per CORESET. For the interleaving parameter C, if it is per spectrum, the value of C needs to be calculated based on the CORESET resources within the spectrum (i.e., the number of REGs within each CORESET part) before interleaving. Calculating the C value based on the mapping obtained per CORESET part allows for a more even distribution of resources within the frequency domain of the CORESET part, resulting in better frequency domain diversity gain.

[0392] Option 6-2, interleaving is performed throughout the entire CORESET (NR legacy behavior).

[0393] The target CORESET can be configured with the following precoder methods: all continuous RB-based precoder, RE bundle-level precoder, per-spectrum precoder, and per-spectrum group precoder. Spectrum-based precoder reduces UE processing complexity compared to RE bundle-based precoder; spectrum-based precoder improves channel estimation accuracy compared to all continuous RB-based precoder.

[0394] The network side configures the CORESET precoder to be either per-spectrum precoding or per-spectrum group precoding. Optionally, when the UE supports spectrum-based precoding, the network side can configure the UE to use spectrum-based precoding.

[0395] The target CORESET occupies PRB 0-5 on spectrum 1, and the target CORESET occupies PRB 0-5 on spectrum 2, as shown in Figure 22.

[0396] It's important to note that NR defines both an all-continuous RB-based precoder and a RE bundle-level precoder. The RE bundle-level precoder uses one precoder for each REG bundle, while the all-continuous RB-based precoder uses a single precoder for all resources within the CORESET. The REG bundle-based precoder scheme consumes more UE resources. Introducing a spectrum-based precoder can balance the complexity and accuracy of UE channel estimation.

[0397] Example 7, taking a target frequency domain unit as a spectrum and multiple spectra with different time domain sizes as an example, shows that the target CORESET occupies two spectra with different time domain resource sizes. This solves the problem of insufficient frequency domain resources within a single spectrum leading to limited coverage or a limited number of UEs, achieving gains in improving coverage and / or increasing UE capacity.

[0398] Option 7-1: Spectrum 1: 5MHz, Spectrum 2: 10MHz.

[0399] As shown in Figure 23, CORESET part 1 in spectrum 1: 30KHz, 3 OS, 6 PRBs; (UE1 may be idle in spectrum 1, with a preferred bandwidth of 5MHz) CORESET part 2 in spectrum 2: 30KHz, 2 OS, 18 PRBs.

[0400] It should be noted that on both spectrum 1 and spectrum 2, CORESET can be configured with 6 PRBs as a group of PRBs. However, the interleaving parameter C needs to be enhanced; in this case, the value of C is not an integer.

[0401] Example 8 uses the target frequency domain unit as the spectrum and determines the frequency domain resources of the target core set across multiple spectra as an example. This solves the problem of insufficient frequency domain resources within a single spectrum leading to limited coverage or a limited number of UEs, achieving gains in improving coverage and / or increasing UE capacity.

[0402] Solution 8-1 maps CORESET resources starting from the lowest PRB of each spectrum or according to the configured RB offset. For example, RB offset 1 corresponds to the starting position of the CORESET in spectrum 1, and RB offset 2 corresponds to the starting position of the CORESET in spectrum 2.

[0403] As shown in Figure 24, resources with less than one CORESET frequency domain resource configuration granularity (e.g., 6 PRBs) remaining within a Spectrum are considered non-configurable resources. Alternatively, as shown in Figure 24A, remaining frequency domain resources within a Spectrum are treated as a specific resource and configured as 0, indicating a non-CORESET resource; if configured as 1, the specific resource is a resource within a CORESET (in this case, the effect is the same as in Example 5 within a single Spectrum); or the remaining resource indicator is configured as 0. Alternatively, as shown in Figure 24B, resources are indicated with CORESET frequency domain configuration granularity. If the indicated resource is available for CORESET, the resource within the Spectrum is considered available; or, as shown in Figure 24C, the indicated resource is an available resource (i.e., includes resources within the Spectrum and resources outside the Spectrum); or resources with less than one configuration granularity are configured as 0. Scheme 8-2 considers the two subbands / FPs together as a whole to divide the granular grid. The gap between Spectrums is not within the indication range, as shown in Figure 25. In this case, if CCE can cross the spectrum, there is no problem; if not, there will be fewer available resources for this mapping.

[0404] The difference between Scheme 8-1 and Scheme 8-2 is that each spectrum starts from the lowest PRB to consider the resource mapping of the CORESET, which can reduce resource waste within the spectrum.

[0405] In scheme 8-3, the gap in spectrum is also within the scope of CORESET's instructions.

[0406] The CORESET bitmap is applied between the lowest and highest PRBs of spectrum 1 and spectrum 2, including the gap, as shown in Figure 26. The gap in Figure 26 represents the gap between spectra and is only an example. In reality, the gap may be larger or smaller; this is not a limitation.

[0407] In scheme 8-4, the gap in spectrum is also within the scope of CORESET's instructions.

[0408] Map CORESET resources starting from the lowest PRB of each spectrum or the configured RB offset. For example, RB offset 1 corresponds to the starting position of the CORESET in spectrum 1, and RB offset 2 corresponds to the starting position of the CORESET in spectrum 2.

[0409] If there are fewer than one remaining CORESET frequency domain resource in Spectrum, the configuration granularity (e.g., 6PRB) is 1 bit in the CORESET bitmap of a specific resource to indicate whether it is available.

[0410] The resource indicator in the CORESET bitmap indicates whether resources in the gap are available. It can be multiple bits (as opposed to the size of the gap and / or the configuration granularity of CORESET) or 1 bit indicating the resource configuration within the gap, as shown in Figure 27.

[0411] In scheme 8-5, the gap in spectrum is also within the scope of CORESET's instructions.

[0412] Map CORESET resources starting from the lowest PRB of each spectrum or the configured RB offset. For example, RB offset 1 corresponds to the starting position of the CORESET in spectrum 1, and RB offset 2 corresponds to the starting position of the CORESET in spectrum 2.

[0413] CORESET's bitmap is applied between the lowest and highest PRBs of spectrum 1 and spectrum 2, including the gap.

[0414] The CORESET bitmap maps from the lowest PRB of spectrum 1 to the PRB preceding the lowest PRB of spectrum 2 (i.e., the last PRB of the gap). Resources less than one CORESET in frequency domain are indicated with 1 bit. (For example, in Figure 28, the last 2 PRBs remaining in the gap are indicated with 1 bit), or resources less than one CORESET in frequency domain are not indicated (i.e., they are not considered CORESET resources by default).

[0415] The CORESET bitmap maps from the lowest PRB of spectrum 2 to the highest PRB of spectrum. If there is less than one CORESET frequency domain resource mapping granularity, it is indicated with 1 bit. Alternatively, resources less than one CORESET frequency domain granularity are not indicated (i.e., they are not considered CORESET resources by default).

[0416] The wireless communication method provided in this application can be executed by a wireless communication device. This application uses an example of a wireless communication device executing the wireless communication method to illustrate the wireless communication device provided in this application.

[0417] This application provides a wireless communication device. As an example, the wireless communication device may be a communication equipment or a component within a communication equipment, such as a chip. The communication equipment may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0418] The wireless communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0419] Referring to Figure 29, when the wireless communication device is a communication device or a component of a communication device, the wireless communication device 300 includes:

[0420] Processing module 301 is used to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information;

[0421] The first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type.

[0422] In some embodiments, the resource information of the target frequency domain cell includes the bandwidth of the target frequency domain cell and / or the location of the target frequency domain cell;

[0423] The target CORESET is located within one or more target frequency domain units.

[0424] In some embodiments, the resource indication information of the CORESET includes at least one of the following: frequency domain resource indication information, time domain resource indication information, and time-frequency domain resource indication information;

[0425] The frequency domain resource indication information is used to indicate at least one of the following:

[0426] The frequency domain resource size of the target CORESET, the frequency domain resource location of the target CORESET, the frequency domain resource size of each CORESET portion in the target CORESET, the frequency domain resource location of each CORESET portion in the target CORESET, the frequency domain resource size of each CORESET portion group in the target CORESET, and the frequency domain resource location of each CORESET portion group in the target CORESET;

[0427] The time-domain resource indication information is used to indicate at least one of the following:

[0428] The temporal resource size of the target CORESET, the temporal resource location of the target CORESET, the temporal resource size of each CORESET portion in the target CORESET, the temporal resource location of each CORESET portion in the target CORESET, the temporal resource size of each CORESET portion group in the target CORESET, and the temporal resource location of each CORESET portion group in the target CORESET;

[0429] The time-frequency domain resource indication information is used to indicate at least one of the following:

[0430] The time-frequency domain resource size of the target CORESET, the time-frequency domain resource location of the target CORESET, the time-frequency domain resource size of each CORESET portion in the target CORESET, the time-frequency domain resource location of each CORESET portion in the target CORESET, the time-frequency domain resource size of each CORESET portion group in the target CORESET, and the time-frequency domain resource location of each CORESET portion group in the target CORESET;

[0431] The target CORESET includes at least two CORESET parts or at least two groups of CORESET parts, and a group of CORESET parts includes at least two CORESET parts.

[0432] In some embodiments, the resource mapping information of the CORESET includes at least one of the following:

[0433] Mapping method, mapping order;

[0434] The mapping method includes at least one of the following: interleaved mapping method and non-interleaved mapping method.

[0435] In some embodiments, the target CORESET control channel element (CCE) satisfies at least one of the following:

[0436] The size of CCE is 6, the size of CCE is K or K*N1, the size of CCE is K / N1, the size of CCE is the size of the i-th sub-time domain resource, the size of CCE is a common multiple of the size of the i-th sub-time domain resource and 6, the size of CCE is a common multiple of K and 6, the size of CCE is determined based on the size of the target frequency domain unit, the size of CCE is determined based on the time domain resources of CORESET, the size of CCE is determined based on the frequency domain resources of CORESET, the size of CCE is determined based on a portion of CORESET, the size of CCE is determined based on a group of CORESET portions, the size of CCE is determined based on the target frequency domain unit, and the size of CCE is determined based on the sub-time domain resources of CORESET.

[0437] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

[0438] In some embodiments, the REG set of the target CORESET satisfies at least one of the following:

[0439] The REG set size is 2, the REG set size is 3, the REG set size is 6, the REG set size is K, the REG set size is K / N1, the REG set size is the size of the i-th sub-time domain resource, the REG set size is a common multiple of the size of the i-th sub-time domain resource and 6, the REG set size is a common multiple of the size of the i-th sub-time domain resource, the REG set size is a common multiple of K and 6, the REG set size is determined based on the time domain resources of the CORESET, the REG set size is determined based on the frequency domain resources of the CORESET, the REG set size is the size of the target CORESET CCE, the REG set size is agreed upon by the protocol, the REG set size is configured by the network side, the REG set size is determined based on the aggregation level, the REG set size is determined based on the CORESET portion, the REG set size is determined based on the CORESET portion group, and the REG set size is determined based on the sub-time domain resources of the CORESET.

[0440] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

[0441] In some embodiments, the interleaving parameter R of the target CORESET satisfies at least one of the following:

[0442] The size of the interleaving parameter R is 2, the size of the interleaving parameter R is 3, the size of the interleaving parameter R is 6, the size of the interleaving parameter R is K, the size of the interleaving parameter R is K / N1, the size of the interleaving parameter R is the size of the i-th sub-time domain resource, the size of the interleaving parameter R is determined based on the CORESET part, the size of the interleaving parameter R is determined based on the CORESET part group, the size of the interleaving parameter R is determined based on the target frequency domain unit, and the size of the interleaving parameter R is determined based on the sub-time domain resources of the CORESET.

[0443] Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

[0444] In some embodiments, the resource mapping information of the CORESET includes the mapping order;

[0445] The mapping order includes at least one of the following:

[0446] Time-domain resources first, then frequency-domain resources;

[0447] Frequency domain resources first, then time domain resources;

[0448] The i-th sub-time domain resource, frequency domain resource, the (i+1)-th sub-time domain resource, frequency domain resource, ..., the N1-th sub-time domain resource;

[0449] The j-th sub-frequency domain resource, time domain resource, the (j+1)-th sub-frequency domain resource, time domain resource, ..., the N2-th sub-frequency domain resource;

[0450] The i-th sub-time domain resource, the j-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, the (j+1)-th sub-frequency domain resource, ..., the N1-th sub-time domain resource, and the N2-th sub-frequency domain resource;

[0451] The j-th sub-frequency domain resource, the ith sub-time domain resource, the (j+1)-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, ..., the N2-th sub-frequency domain resource, and the N1-th sub-time domain resource;

[0452] The time-frequency domain resources of the target CORESET include N1 sub-time domain resources and N2 sub-frequency domain resources, where N1 is an integer greater than 1 and N2 is an integer greater than 1. The i-th sub-time domain resource is the i-th sub-time domain resource among the N1 sub-time domain resources, and the j-th sub-frequency domain resource is the j-th sub-time domain resource among the N2 sub-frequency domain resources.

[0453] In some embodiments, the mapping order is determined based on CORESET, or the mapping order is determined based on a portion of CORESET, or the mapping order is determined based on a group of CORESET portions, or the mapping order is determined based on a target frequency domain unit, or the mapping order is determined based on sub-time domain resources.

[0454] In some embodiments, the mapping order is the resource mapping order of the CCE, or the mapping order is the resource mapping order of the REG set, or the mapping order is the resource mapping order of the REG within the CCE, or the mapping order is the resource mapping order of the REG within the REG set, or the mapping order is the resource mapping order of the REG within the CORESET.

[0455] In some embodiments, the N1 sub-time domain resources are determined based on the target frequency domain unit, or the N1 sub-time domain resources are determined based on the CORESET configuration;

[0456] And / or,

[0457] The N1 sub-time domain resources are sequentially associated with the target frequency domain units according to the identification order of the target frequency domain units;

[0458] And / or,

[0459] The different sub-time domain resources in the N1 sub-time domain resources may have the same or different sizes, and / or, the different sub-time domain resources in the N1 sub-time domain resources do not overlap in the time domain, and / or, the size of the sub-time domain resources in the N1 sub-time domain resources is 2, 3 or K / N1, and / or, the size of each sub-time domain resource in the N1 sub-time domain resources is agreed upon by the protocol or configured by the network side.

[0460] In some embodiments, the resource mapping information of the CORESET includes the mapping method, and the mapping method is an interleaving mapping method. The time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit, or the time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit group, or the time-frequency domain resources of the target CORESET are interleaved within a portion of the CORESET, or the time-frequency domain resources of the target CORESET are interleaved within a portion group of the CORESET.

[0461] In some embodiments, the interleaving parameters of the interleaving mapping method satisfy at least one of the following:

[0462] The size of CCE is determined based on the target frequency domain cell, or the size of CCE is determined based on the target frequency domain cell group, or the size of CCE is determined based on CORESET;

[0463] The size L of the REG set is determined based on the target frequency domain unit, or the size L of the REG set is determined based on the target frequency domain unit group, or the size L of the REG set is determined based on CORESET.

[0464] The magnitude of the interleaving parameter R is determined based on the target frequency domain cell, or the magnitude of the interleaving parameter R is determined based on the target frequency domain cell group, or the magnitude of the interleaving parameter R is determined based on CORESET;

[0465] The interleaving parameter C is determined based on the target frequency domain cell, or the interleaving parameter C is determined based on the target frequency domain cell group, or the interleaving parameter C is determined based on CORESET;

[0466] Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units;

[0467] The resource unit is one of the following: REG, resource element RE, physical resource block PRB, physical resource group PRG.

[0468] In some embodiments, the time-domain resources of the target CORESET are determined based on the target frequency-domain units; and / or,

[0469] The frequency domain resources of the target CORESET are determined based on the target frequency domain cells; and / or,

[0470] The size of the time-domain resources of the target CORESET is determined based on the target frequency-domain units; and / or,

[0471] The size of the frequency domain resources of the target CORESET is determined based on the target frequency domain cells; and / or,

[0472] The frequency domain resources of the target CORESET are determined based on the priority of the target frequency domain cells; and / or,

[0473] The frequency domain resources of the target CORESET are determined based on the cascading order of the target frequency domain cells; and / or,

[0474] The size of the CORESET portion in the target CORESET is determined based on the target frequency domain units; and / or,

[0475] The size of the CORESET portion group in the target CORESET is determined based on the target frequency domain unit.

[0476] In some embodiments, the frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency unit; or,

[0477] The resources of the target CORESET are the intersection of the resources of the CORESET determined based on the resource indication information of the CORESET and the resources of the target frequency domain unit; or,

[0478] The frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit, and the interleaving parameter C corresponding to the frequency domain resources of the target CORESET is an integer.

[0479] Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units;

[0480] The resource unit is one of the following: REG, RE, PRB, PRG.

[0481] In some embodiments, the frequency domain resources indicated by the resource indication information of CORESET start from PRB 0 of the target frequency domain cell;

[0482] Alternatively, if the number of target frequency domain units where the target CORESET is located is greater than or equal to 2, the frequency domain resources indicated by the resource indication information of the CORESET shall start from the minimum PRB of at least two target frequency domain units;

[0483] Alternatively, if the number of target frequency domain units where the target CORESET is located is greater than or equal to 2, the frequency domain resources indicated by the resource indication information of the CORESET shall be based on the minimum PRB of each target frequency domain unit.

[0484] In some embodiments, the size of the resource indication information of the CORESET is determined based on at least one of the following: the frequency domain resource indication granularity of the target CORESET, the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols occupied by the target CORESET, the target frequency domain cell in which the target CORESET is located, the range of the minimum and maximum PRBs of the target frequency domain cell in which the target CORESET is located, the total number of PRBs in the target frequency domain cell in which the target CORESET is located, and the relationship between the frequency domain resource indication granularity of the target CORESET and the target frequency domain cell;

[0485] And / or,

[0486] The frequency domain resource indication granularity of the target CORESET is M PRBs, where the M PRBs are either consecutive resources or non-consecutive resources, and M is a positive integer.

[0487] And / or,

[0488] The frequency domain resource indication granularity of the target CORESET is determined based on the target frequency domain cells, or the frequency domain resource indication granularity of the target CORESET is determined based on the number of OFDM symbols occupied by the target CORESET.

[0489] In some embodiments, the M PRBs are resources spanning the target frequency domain.

[0490] In some embodiments, the aggregation level of the CORESET includes at least one of the following: 1, 2, 3, 4, 5, 6, 7, 8, 16, 32, 64, 128;

[0491] And / or,

[0492] The aggregation level of the CORESET is determined based on the size of the REG set, or the aggregation level of the CORESET is determined based on the number of OFDM symbols occupied by the target CORESET;

[0493] And / or,

[0494] The aggregation level of the CORESET is determined based on the CORESET, or the aggregation level of the CORESET is determined based on a portion of the CORESET, or the aggregation level of the CORESET is determined based on a group of CORESET portions, or the aggregation level of the CORESET is determined based on the target frequency domain unit, or the aggregation level of the CORESET is determined based on sub-time domain resources.

[0495] In some embodiments, the number of physical downlink control channel (PDCCH) candidates within the target CORESET is determined based on at least one of the following:

[0496] The aggregation level of the CORESET;

[0497] The number of CCEs within the CORESET section;

[0498] Number of resource units within the CORESET section;

[0499] The number of CCEs within the CORESET section;

[0500] Number of resource units within a CORESET group;

[0501] The number of CCEs within the target frequency domain cell;

[0502] The number of resource units within the target frequency domain unit;

[0503] The number of CCEs within the target frequency domain cell group;

[0504] The number of resource units within the target frequency domain unit group;

[0505] Number of CCEs within a sub-time domain unit;

[0506] The number of resource units within a sub-time domain unit;

[0507] The resource unit is one of the following: REG, RE, PRB, PRG.

[0508] In some embodiments, the resources of the target frequency domain cell corresponding to the target CORESET are determined based on at least one of the following:

[0509] Quality of Service (QoS), aggregation level, and terminal capabilities.

[0510] In some embodiments, the precoding corresponding to the target CORESET is determined based on the CORESET, or the precoding corresponding to the target CORESET is determined based on a portion of the CORESET, or the precoding corresponding to the target CORESET is determined based on a group of CORESET portions, or the precoding corresponding to the target CORESET is determined based on a target frequency domain unit, or the precoding corresponding to the target CORESET is determined based on a sub-time domain unit.

[0511] In some embodiments, the first information is determined based on at least one of the following:

[0512] Subcarrier spacing (SCS), cyclic prefix (CP).

[0513] In some embodiments, if the target CORESET is CORESET 0, or the target CORESET is the CORESET of the target frequency domain unit for initial access, or the target CORESET is the CORESET of the receiving system information block SIB1, the time-frequency domain resources of the target CORESET are defined by the protocol, and / or the size of the target CORESET CCE is defined by the protocol, and / or the size of the REG set of the target CORESET is defined by the protocol, and / or the size of the interleaving parameter R of the target CORESET is defined by the protocol, and / or the aggregation level corresponding to the target CORESET is defined by the protocol.

[0514] In some embodiments, the transmission of the PDCCH within the target CORESET satisfies at least one of the following:

[0515] The transmission of PDCCH in CORESET part P is a repetition of the transmission of PDCCH in CORESET part Q;

[0516] The transmission of PDCCH in the CORESET portion of the target frequency domain unit P is a repetition of the transmission of PDCCH in the CORESET portion of the target frequency domain unit Q;

[0517] The transmission of PDCCH within the CORESET portion of time-domain resource set P is a repetition of the transmission of PDCCH within the CORESET portion of time-domain resource set Q;

[0518] Where P and Q are both integers greater than or equal to 0.

[0519] In some embodiments, the terminal capabilities include at least one of the following:

[0520] The terminal supports precoding based on the target frequency domain unit, or the terminal supports precoding based on the CORESET portion, or the terminal supports precoding based on the CORESET portion group;

[0521] The terminal supports REG set sizes of 2, 3, 6, K, K / N1, the size of the i-th sub-time domain resource, a common multiple of the size of the i-th sub-time domain resource and 6, a common multiple of the sizes of all sub-time domain resources, a common multiple of K and 6, a size determined based on the time domain resources of the CORESET, a size determined based on the frequency domain resources of the CORESET, a size equal to the size of the CCE corresponding to the target CORESET, or a size agreed upon by the protocol. The size of the REG set can be configured by the network side, determined based on the aggregation level, determined based on the CORESET portion, determined based on the CORESET portion group, or determined based on the sub-temporal resources of the CORESET; wherein, the temporal resource size of the target CORESET is K, and the temporal resources of the target CORESET include N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1;

[0522] The terminal supports 4, 5, 6, 7, 8, 12, or 14 OFDM symbols for CORESET time-domain resources, or the terminal supports one time slot for CORESET time-domain resources.

[0523] The terminal supports repeated transmission of CORESET;

[0524] The terminal supports the target frequency domain unit;

[0525] The terminal supports bandwidth of X MHz or X PRBs, and / or the terminal supports bandwidth of less than X MHz or X PRBs, where X is a non-negative number, and X is determined by the protocol or configured by the network side.

[0526] The terminal supports NTN (Network Telecommunication) services.

[0527] Does the terminal's CORESET support at least two carriers or at least two target frequency domain units, or does the terminal's CORESET support non-contiguous spectrum resources?

[0528] Therefore, in this embodiment of the application, the communication device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information; wherein, the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type. Specifically, the communication equipment determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information (at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type). It can expand the resources of the CORESET (such as expanding the resources of the CORESET within the target frequency domain unit), and / or expand the frequency domain resource indication granularity of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET, thereby improving the performance of the CORESET, increasing the coverage of control information in the communication system, and increasing the capacity of terminals in the communication system.

[0529] The wireless communication device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0530] As shown in Figure 30, this application embodiment also provides a communication device 400, including a processor 401 and a memory 402. The memory 402 stores a program or instructions that can run on the processor 401. For example, when the program or instructions are executed by the processor 401, they implement the various steps performed by the communication device in the above-described wireless communication method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0531] This 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 used to run programs or instructions to implement the steps in the method embodiment shown in FIG4. This terminal embodiment corresponds to the above-described communication device-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the wireless communication device 300 shown in FIG29.

[0532] Specifically, Figure 31 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0533] The terminal 500 includes, but is not limited to, at least some of the following components: radio frequency unit 501, network module 502, audio output unit 503, input unit 504, sensor 505, display unit 506, user input unit 507, interface unit 508, memory 509, and processor 510.

[0534] Those skilled in the art will understand that terminal 500 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 510 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 31 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0535] It should be understood that, in this embodiment, the input unit 504 may include a graphics processor 5041 and a microphone 5042. The graphics processor 5041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 507 includes at least one of a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0536] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 501 can transmit it to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network-side device. Typically, the radio frequency unit 501 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0537] The memory 509 can be used to store software programs or instructions, as well as various data. The memory 509 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 509 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can 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 memory bus RAM (DRRAM). The memory 509 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0538] Processor 510 may include one or more processing units; optionally, processor 510 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 510.

[0539] In some embodiments, the processor 510 is configured to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on first information; wherein the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type.

[0540] Therefore, in this embodiment, the terminal determines the time-frequency domain resources and / or resource mapping method of the target CORESET based on the first information; wherein, the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type. Specifically, the terminal determines the time-frequency domain resources and / or resource mapping method of the target CORESET based on the first information (at least one of the resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type), which can expand the resources of the CORESET (such as expanding the resources of the CORESET within the target frequency domain unit), and / or expand the frequency domain resource indication granularity of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET, thereby improving the performance of the CORESET, increasing the coverage of control information in the communication system, and increasing the capacity of terminals in the communication system.

[0541] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0542] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG4. This network-side device embodiment corresponds to the method embodiment executed by the above-described communication device. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0543] This application also provides a network-side device, which may be the wireless communication device 300 shown in FIG29.

[0544] Specifically, as shown in Figure 32, the network-side device 600 includes: an antenna 61, a radio frequency (RF) device 62, a baseband device 63, a processor 64, and a memory 65. The antenna 61 is connected to the RF device 62. In the uplink direction, the RF device 62 receives information through the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be transmitted and sends it to the RF device 62. The RF device 62 processes the received information and then transmits it through the antenna 61.

[0545] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 63, which includes a baseband processor.

[0546] The baseband device 63 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG32. One of the chips is, for example, a baseband processor, which is connected to the memory 65 via a bus interface to call the program in the memory 65 and execute the operation of the network-side device shown in the above method embodiment.

[0547] The network-side device may also include a network interface 66, such as a Common Public Radio Interface (CPRI).

[0548] Specifically, the network-side device 600 in this application embodiment further includes: instructions or programs stored in memory 65 and executable on processor 64. Processor 64 calls the instructions or programs in memory 65 to execute the methods executed by each module shown in FIG29 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0549] In some embodiments, the processor 64 is configured to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on first information; wherein the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type.

[0550] Therefore, in this embodiment of the application, the network-side device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information; wherein, the first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type. Specifically, the network-side device determines the time-frequency domain resources of the target CORESET and / or the resource mapping method of the target CORESET based on the first information (at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capability, frequency domain range, and service type). It can expand the resources of the CORESET (such as expanding the resources of the CORESET within the target frequency domain unit), and / or expand the granularity of the frequency domain resource indication of the CORESET, and / or expand the resource mapping information of the CORESET, and / or expand the aggregation level of the CORESET, thereby improving the performance of the CORESET, increasing the coverage of control information in the communication system, and increasing the capacity of terminals in the communication system.

[0551] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described wireless communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0552] The processor mentioned above is the processor in the communication device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0553] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described wireless communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0554] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0555] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described wireless communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0556] This application also provides a wireless communication system, including: a terminal and a network-side device. The terminal can be used to execute the steps performed by the communication device in the wireless communication method described above, or the network-side device can be used to execute the steps performed by the communication device in the wireless communication method described above.

[0557] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0558] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0559] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method of wireless communication, wherein, include: The communication device determines the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information; The first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capabilities, frequency domain range, and service type.

2. The method according to claim 1, wherein, The resource information of the target frequency domain cell includes the bandwidth of the target frequency domain cell and / or the location of the target frequency domain cell; The target CORESET is located within one or more target frequency domain units.

3. The method according to claim 1 or 2, wherein, The resource indication information of the CORESET includes at least one of the following: frequency domain resource indication information, time domain resource indication information, and time-frequency domain resource indication information; The frequency domain resource indication information is used to indicate at least one of the following: The frequency domain resource size of the target CORESET, the frequency domain resource location of the target CORESET, the frequency domain resource size of each CORESET portion in the target CORESET, the frequency domain resource location of each CORESET portion in the target CORESET, the frequency domain resource size of each CORESET portion group in the target CORESET, and the frequency domain resource location of each CORESET portion group in the target CORESET; The time-domain resource indication information is used to indicate at least one of the following: The temporal resource size of the target CORESET, the temporal resource location of the target CORESET, the temporal resource size of each CORESET portion in the target CORESET, the temporal resource location of each CORESET portion in the target CORESET, the temporal resource size of each CORESET portion group in the target CORESET, and the temporal resource location of each CORESET portion group in the target CORESET; The time-frequency domain resource indication information is used to indicate at least one of the following: The time-frequency domain resource size of the target CORESET, the time-frequency domain resource location of the target CORESET, the time-frequency domain resource size of each CORESET portion in the target CORESET, the time-frequency domain resource location of each CORESET portion in the target CORESET, the time-frequency domain resource size of each CORESET portion group in the target CORESET, and the time-frequency domain resource location of each CORESET portion group in the target CORESET; The target CORESET includes at least two CORESET parts or at least two groups of CORESET parts, and a group of CORESET parts includes at least two CORESET parts.

4. The method according to any one of claims 1 to 3, wherein, The resource mapping information of CORESET includes at least one of the following: Mapping method, mapping order; The mapping method includes at least one of the following: interleaved mapping method and non-interleaved mapping method.

5. The method according to any one of claims 1 to 4, wherein, The target CORESET control channel element (CCE) satisfies at least one of the following: The size of CCE is 6, the size of CCE is K or K*N1, the size of CCE is K / N1, the size of CCE is the size of the i-th sub-time domain resource, the size of CCE is a common multiple of the size of the i-th sub-time domain resource and 6, the size of CCE is a common multiple of K and 6, the size of CCE is determined based on the size of the target frequency domain unit, the size of CCE is determined based on the time domain resources of CORESET, the size of CCE is determined based on the frequency domain resources of CORESET, the size of CCE is determined based on a portion of CORESET, the size of CCE is determined based on a group of CORESET portions, the size of CCE is determined based on the target frequency domain unit, and the size of CCE is determined based on the sub-time domain resources of CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

6. The method according to any one of claims 1 to 5, wherein, The resource element set REG of the target CORESET satisfies at least one of the following: The REG set size is 2, the REG set size is 3, the REG set size is 6, the REG set size is K, the REG set size is K / N1, the REG set size is the size of the i-th sub-time domain resource, the REG set size is a common multiple of the size of the i-th sub-time domain resource and 6, the REG set size is a common multiple of the size of the i-th sub-time domain resource, the REG set size is a common multiple of K and 6, the REG set size is determined based on the time domain resources of the CORESET, the REG set size is determined based on the frequency domain resources of the CORESET, the REG set size is the size of the target CORESET CCE, the REG set size is agreed upon by the protocol, the REG set size is configured by the network side, the REG set size is determined based on the aggregation level, the REG set size is determined based on the CORESET portion, the REG set size is determined based on the CORESET portion group, and the REG set size is determined based on the sub-time domain resources of the CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

7. The method according to any one of claims 1 to 6, wherein, The interleaving parameter R of the target CORESET satisfies at least one of the following: The size of the interleaving parameter R is 2, the size of the interleaving parameter R is 3, the size of the interleaving parameter R is 6, the size of the interleaving parameter R is K, the size of the interleaving parameter R is K / N1, the size of the interleaving parameter R is the size of the i-th sub-time domain resource, the size of the interleaving parameter R is determined based on the CORESET part, the size of the interleaving parameter R is determined based on the CORESET part group, the size of the interleaving parameter R is determined based on the target frequency domain unit, and the size of the interleaving parameter R is determined based on the sub-time domain resources of the CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

8. The method according to any one of claims 1 to 7, wherein, The resource mapping information of CORESET includes the mapping order; The mapping order includes at least one of the following: Time-domain resources first, then frequency-domain resources; Frequency domain resources first, then time domain resources; The i-th sub-time domain resource, frequency domain resource, the (i+1)-th sub-time domain resource, frequency domain resource, ..., the N1-th sub-time domain resource; The j-th sub-frequency domain resource, time domain resource, the (j+1)-th sub-frequency domain resource, time domain resource, ..., the N2-th sub-frequency domain resource; The i-th sub-time domain resource, the j-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, the (j+1)-th sub-frequency domain resource, ..., the N1-th sub-time domain resource, and the N2-th sub-frequency domain resource; The j-th sub-frequency domain resource, the ith sub-time domain resource, the (j+1)-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, ..., the N2-th sub-frequency domain resource, and the N1-th sub-time domain resource; The time-frequency domain resources of the target CORESET include N1 sub-time domain resources and N2 sub-frequency domain resources, where N1 is an integer greater than 1 and N2 is an integer greater than 1. The i-th sub-time domain resource is the i-th sub-time domain resource among the N1 sub-time domain resources, and the j-th sub-frequency domain resource is the j-th sub-time domain resource among the N2 sub-frequency domain resources.

9. The method according to claim 8, wherein, The mapping order is determined based on CORESET, or the mapping order is determined based on a portion of CORESET, or the mapping order is determined based on a group of CORESET portions, or the mapping order is determined based on the target frequency domain unit, or the mapping order is determined based on sub-time domain resources.

10. The method according to claim 8 or 9, wherein, The mapping order is either the resource mapping order of CCE, or the resource mapping order of REG set, or the resource mapping order of REG within CCE, or the resource mapping order of REG within REG set, or the resource mapping order of REG within CORESET.

11. The method according to any one of claims 5 to 10, wherein, The N1 sub-time domain resources are determined based on the target frequency domain unit, or the N1 sub-time domain resources are determined based on the CORESET configuration; And / or, The N1 sub-time domain resources are sequentially associated with the target frequency domain units according to the identification order of the target frequency domain units; And / or, The different sub-time domain resources in the N1 sub-time domain resources may have the same or different sizes, and / or, the different sub-time domain resources in the N1 sub-time domain resources do not overlap in the time domain, and / or, the size of the sub-time domain resources in the N1 sub-time domain resources is 2, 3 or K / N1, and / or, the size of each sub-time domain resource in the N1 sub-time domain resources is agreed upon by the protocol or configured by the network side.

12. The method according to any one of claims 1 to 6, wherein, The resource mapping information of the CORESET includes the mapping method, and the mapping method is an interleaving mapping method. The time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit, or the time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit group, or the time-frequency domain resources of the target CORESET are interleaved within a portion of the CORESET, or the time-frequency domain resources of the target CORESET are interleaved within a portion group of the CORESET.

13. The method according to claim 12, wherein, The interleaving parameters of the interleaving mapping method satisfy at least one of the following: The size of CCE is determined based on the target frequency domain cell, or the size of CCE is determined based on the target frequency domain cell group, or the size of CCE is determined based on CORESET; The size L of the REG set is determined based on the target frequency domain unit, or the size L of the REG set is determined based on the target frequency domain unit group, or the size L of the REG set is determined based on CORESET. The magnitude of the interleaving parameter R is determined based on the target frequency domain cell, or the magnitude of the interleaving parameter R is determined based on the target frequency domain cell group, or the magnitude of the interleaving parameter R is determined based on CORESET; The interleaving parameter C is determined based on the target frequency domain cell, or the interleaving parameter C is determined based on the target frequency domain cell group, or the interleaving parameter C is determined based on CORESET; Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units; The resource unit is one of the following: REG, resource element RE, physical resource block PRB, physical resource group PRG.

14. The method according to any one of claims 1 to 13, wherein, The time-domain resources of the target CORESET are determined based on the target frequency-domain units; and / or, The frequency domain resources of the target CORESET are determined based on the target frequency domain cells; and / or, The size of the time-domain resources of the target CORESET is determined based on the target frequency-domain units; and / or, The size of the frequency domain resources of the target CORESET is determined based on the target frequency domain cells; and / or, The frequency domain resources of the target CORESET are determined based on the priority of the target frequency domain cells; and / or, The frequency domain resources of the target CORESET are determined based on the cascading order of the target frequency domain cells; And / or, The size of the CORESET portion in the target CORESET is determined based on the target frequency domain units; and / or, The size of the CORESET portion group in the target CORESET is determined based on the target frequency domain unit.

15. The method according to any one of claims 1 to 14, wherein, The frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET and the frequency domain resources of the target frequency unit, determined based on the resource indication information of the CORESET. or, The resources of the target CORESET are the intersection of the resources of the CORESET and the resources of the target frequency domain unit, determined based on the resource indication information of the CORESET. or, The frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit, and the interleaving parameter C corresponding to the frequency domain resources of the target CORESET is an integer. Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units; The resource unit is one of the following: REG, RE, PRB, PRG.

16. The method according to claim 15, wherein, The frequency domain resources indicated by the resource indication information of CORESET start from PRB 0 of the target frequency domain unit; Alternatively, if the number of target frequency domain units where the target CORESET is located is greater than or equal to 2, the frequency domain resources indicated by the resource indication information of the CORESET shall start from the minimum PRB of at least two target frequency domain units; Alternatively, if the number of target frequency domain units where the target CORESET is located is greater than or equal to 2, the frequency domain resources indicated by the resource indication information of the CORESET shall be based on the minimum PRB of each target frequency domain unit.

17. The method according to any one of claims 1 to 16, wherein, The size of the resource indication information of the CORESET is determined based on at least one of the following: the frequency domain resource indication granularity of the target CORESET, the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols occupied by the target CORESET, the target frequency domain cell in which the target CORESET is located, the range of the minimum and maximum PRBs of the target frequency domain cell in which the target CORESET is located, the total number of PRBs in the target frequency domain cell in which the target CORESET is located, and the relationship between the frequency domain resource indication granularity of the target CORESET and the target frequency domain cell; And / or, The frequency domain resource indication granularity of the target CORESET is M PRBs, where the M PRBs are either consecutive resources or non-consecutive resources, and M is a positive integer. And / or, The frequency domain resource indication granularity of the target CORESET is determined based on the target frequency domain cells, or the frequency domain resource indication granularity of the target CORESET is determined based on the number of OFDM symbols occupied by the target CORESET.

18. The method according to claim 17, wherein, The M PRBs are resources spanning the target frequency domain.

19. The method according to any one of claims 1 to 18, wherein, The aggregation level of the CORESET includes at least one of the following: 1, 2, 3, 4, 5, 6, 7, 8, 16, 32, 64, 128; And / or, The aggregation level of the CORESET is determined based on the size of the REG set, or the aggregation level of the CORESET is determined based on the number of OFDM symbols occupied by the target CORESET; And / or, The aggregation level of the CORESET is determined based on the CORESET, or the aggregation level of the CORESET is determined based on a portion of the CORESET, or the aggregation level of the CORESET is determined based on a group of CORESET portions, or the aggregation level of the CORESET is determined based on the target frequency domain unit, or the aggregation level of the CORESET is determined based on sub-time domain resources.

20. The method of any one of claims 1 to 19, wherein, The number of physical downlink control channel (PDCCH) candidates within the target CORESET is determined based on at least one of the following: The aggregation level of the CORESET; The number of CCEs within the CORESET section; Number of resource units within the CORESET section; The number of CCEs within the CORESET section; Number of resource units within a CORESET group; The number of CCEs within the target frequency domain cell; The number of resource units within the target frequency domain unit; The number of CCEs within the target frequency domain cell group; The number of resource units within the target frequency domain unit group; Number of CCEs within a sub-time domain unit; The number of resource units within a sub-time domain unit; The resource unit is one of the following: REG, RE, PRB, PRG.

21. The method according to any one of claims 1 to 20, wherein, The resources of the target frequency domain cell corresponding to the target CORESET are determined based on at least one of the following: Quality of Service (QoS), aggregation level, and terminal capabilities.

22. The method according to any one of claims 1 to 21, wherein, The precoding corresponding to the target CORESET is determined based on the CORESET, or the precoding corresponding to the target CORESET is determined based on a portion of the CORESET, or the precoding corresponding to the target CORESET is determined based on a group of CORESET portions, or the precoding corresponding to the target CORESET is determined based on the target frequency domain unit, or the precoding corresponding to the target CORESET is determined based on the sub-time domain unit.

23. The method according to any one of claims 1 to 22, wherein, The first information is determined based on at least one of the following: Subcarrier spacing (SCS), cyclic prefix (CP).

24. The method according to any one of claims 1 to 23, wherein, If the target CORESET is CORESET 0, or the target CORESET is the CORESET of the target frequency domain unit for initial access, or the target CORESET is the CORESET of the receiving system information block SIB1, the time-frequency domain resources of the target CORESET are defined by the protocol, and / or the size of the target CORESET CCE is defined by the protocol, and / or the size of the REG set of the target CORESET is defined by the protocol, and / or the size of the interleaving parameter R of the target CORESET is defined by the protocol, and / or the aggregation level corresponding to the target CORESET is defined by the protocol.

25. The method according to any one of claims 1 to 24, wherein, The transmission of PDCCH within the target CORESET satisfies at least one of the following: The transmission of PDCCH in CORESET part P is a repetition of the transmission of PDCCH in CORESET part Q; The transmission of PDCCH in the CORESET portion of the target frequency domain unit P is a repetition of the transmission of PDCCH in the CORESET portion of the target frequency domain unit Q; The transmission of PDCCH within the CORESET portion of time-domain resource set P is a repetition of the transmission of PDCCH within the CORESET portion of time-domain resource set Q; Where P and Q are both integers greater than or equal to 0.

26. The method according to any one of claims 1 to 25, wherein, The terminal capabilities include at least one of the following: The terminal supports precoding based on the target frequency domain unit, or the terminal supports precoding based on the CORESET portion, or the terminal supports precoding based on the CORESET portion group; The terminal supports REG set sizes of 2, 3, 6, K, K / N1, the size of the i-th sub-time domain resource, a common multiple of the size of the i-th sub-time domain resource and 6, a common multiple of the sizes of all sub-time domain resources, a common multiple of K and 6, a size determined based on the time domain resources of the CORESET, a size determined based on the frequency domain resources of the CORESET, a size equal to the size of the CCE corresponding to the target CORESET, or a size agreed upon by the protocol. The size of the REG set can be configured by the network side, determined based on the aggregation level, determined based on the CORESET portion, determined based on the CORESET portion group, or determined based on the sub-temporal resources of the CORESET; wherein, the temporal resource size of the target CORESET is K, and the temporal resources of the target CORESET include N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1; The terminal supports 4, 5, 6, 7, 8, 12, or 14 OFDM symbols for CORESET time-domain resources, or the terminal supports one time slot for CORESET time-domain resources. The terminal supports repeated transmission of CORESET; The terminal supports the target frequency domain unit; The terminal supports bandwidth of X MHz or X PRBs, and / or the terminal supports bandwidth of less than X MHz or X PRBs, where X is a non-negative number, and X is determined by the protocol or configured by the network side. The terminal supports NTN (Network Telecommunication) services. Does the terminal's CORESET support at least two carriers or at least two target frequency domain units, or does the terminal's CORESET support non-contiguous spectrum resources? 27. A wireless communication device, wherein, include: The processing module is used to determine the time-frequency domain resources of the target control resource set CORESET and / or the resource mapping method of the target CORESET based on the first information; The first information includes at least one of the following: resource information of the target frequency domain unit, resource indication information of the CORESET, resource mapping information of the CORESET, aggregation level of the CORESET, terminal capabilities, frequency domain range, and service type.

28. The apparatus according to claim 27, wherein, The resource indication information of the CORESET includes at least one of the following: frequency domain resource indication information, time domain resource indication information, and time-frequency domain resource indication information; The frequency domain resource indication information is used to indicate at least one of the following: The frequency domain resource size of the target CORESET, the frequency domain resource location of the target CORESET, the frequency domain resource size of each CORESET portion in the target CORESET, the frequency domain resource location of each CORESET portion in the target CORESET, the frequency domain resource size of each CORESET portion group in the target CORESET, and the frequency domain resource location of each CORESET portion group in the target CORESET; The time-domain resource indication information is used to indicate at least one of the following: The temporal resource size of the target CORESET, the temporal resource location of the target CORESET, the temporal resource size of each CORESET portion in the target CORESET, the temporal resource location of each CORESET portion in the target CORESET, the temporal resource size of each CORESET portion group in the target CORESET, and the temporal resource location of each CORESET portion group in the target CORESET; The time-frequency domain resource indication information is used to indicate at least one of the following: The time-frequency domain resource size of the target CORESET, the time-frequency domain resource location of the target CORESET, the time-frequency domain resource size of each CORESET portion in the target CORESET, the time-frequency domain resource location of each CORESET portion in the target CORESET, the time-frequency domain resource size of each CORESET portion group in the target CORESET, and the time-frequency domain resource location of each CORESET portion group in the target CORESET; The target CORESET includes at least two CORESET parts or at least two groups of CORESET parts, and a group of CORESET parts includes at least two CORESET parts.

29. The apparatus according to claim 27 or 28, wherein, The target CORESET control channel element (CCE) satisfies at least one of the following: The size of CCE is 6, the size of CCE is K or K*N1, the size of CCE is K / N1, the size of CCE is the size of the i-th sub-time domain resource, the size of CCE is a common multiple of the size of the i-th sub-time domain resource and 6, the size of CCE is a common multiple of K and 6, the size of CCE is determined based on the size of the target frequency domain unit, the size of CCE is determined based on the time domain resources of CORESET, the size of CCE is determined based on the frequency domain resources of CORESET, the size of CCE is determined based on a portion of CORESET, the size of CCE is determined based on a group of CORESET portions, the size of CCE is determined based on the target frequency domain unit, and the size of CCE is determined based on the sub-time domain resources of CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

30. The apparatus according to any one of claims 27 to 29, wherein, The resource element set REG of the target CORESET satisfies at least one of the following: The REG set size is 2, the REG set size is 3, the REG set size is 6, the REG set size is K, the REG set size is K / N1, the REG set size is the size of the i-th sub-time domain resource, the REG set size is a common multiple of the size of the i-th sub-time domain resource and 6, the REG set size is a common multiple of the size of the i-th sub-time domain resource, the REG set size is a common multiple of K and 6, the REG set size is determined based on the time domain resources of the CORESET, the REG set size is determined based on the frequency domain resources of the CORESET, the REG set size is the size of the target CORESET CCE, the REG set size is agreed upon by the protocol, the REG set size is configured by the network side, the REG set size is determined based on the aggregation level, the REG set size is determined based on the CORESET portion, the REG set size is determined based on the CORESET portion group, and the REG set size is determined based on the sub-time domain resources of the CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

31. The apparatus according to any one of claims 27 to 30, wherein, The interleaving parameter R of the target CORESET satisfies at least one of the following: The size of the interleaving parameter R is 2, the size of the interleaving parameter R is 3, the size of the interleaving parameter R is 6, the size of the interleaving parameter R is K, the size of the interleaving parameter R is K / N1, the size of the interleaving parameter R is the size of the i-th sub-time domain resource, the size of the interleaving parameter R is determined based on the CORESET part, the size of the interleaving parameter R is determined based on the CORESET part group, the size of the interleaving parameter R is determined based on the target frequency domain unit, and the size of the interleaving parameter R is determined based on the sub-time domain resources of the CORESET. Wherein, the temporal resource size of the target CORESET is K, and the temporal resource of the target CORESET includes N1 sub-temporal resources, where N1 is an integer greater than 1, K is an integer greater than or equal to 0, K / N1 is an integer greater than or equal to 0, and the i-th sub-temporal resource is the i-th sub-temporal resource among the N1 sub-temporal resources, where i is a positive integer, and 1≤i≤N1.

32. The apparatus according to any one of claims 27 to 31, wherein, The resource mapping information of CORESET includes the mapping order; The mapping order includes at least one of the following: Time-domain resources first, then frequency-domain resources; Frequency domain resources first, then time domain resources; The i-th sub-time domain resource, frequency domain resource, the (i+1)-th sub-time domain resource, frequency domain resource, ..., the N1-th sub-time domain resource; The j-th sub-frequency domain resource, time domain resource, the (j+1)-th sub-frequency domain resource, time domain resource, ..., the N2-th sub-frequency domain resource; The i-th sub-time domain resource, the j-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, the (j+1)-th sub-frequency domain resource, ..., the N1-th sub-time domain resource, and the N2-th sub-frequency domain resource; The j-th sub-frequency domain resource, the ith sub-time domain resource, the (j+1)-th sub-frequency domain resource, the (i+1)-th sub-time domain resource, ..., the N2-th sub-frequency domain resource, and the N1-th sub-time domain resource; The time-frequency domain resources of the target CORESET include N1 sub-time domain resources and N2 sub-frequency domain resources, where N1 is an integer greater than 1 and N2 is an integer greater than 1. The i-th sub-time domain resource is the i-th sub-time domain resource among the N1 sub-time domain resources, and the j-th sub-frequency domain resource is the j-th sub-time domain resource among the N2 sub-frequency domain resources.

33. The apparatus according to any one of claims 27 to 32, wherein, The resource mapping information of the CORESET includes a mapping method, and the mapping method is an interleaving mapping method. The time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit, or the time-frequency domain resources of the target CORESET are interleaved within the target frequency domain unit group, or the time-frequency domain resources of the target CORESET are interleaved within a portion of the CORESET, or the time-frequency domain resources of the target CORESET are interleaved within a portion group of the CORESET.

34. The apparatus according to claim 33, wherein, The interleaving parameters of the interleaving mapping method satisfy at least one of the following: The size of CCE is determined based on the target frequency domain cell, or the size of CCE is determined based on the target frequency domain cell group, or the size of CCE is determined based on CORESET; The size L of the REG set is determined based on the target frequency domain unit, or the size L of the REG set is determined based on the target frequency domain unit group, or the size L of the REG set is determined based on CORESET. The magnitude of the interleaving parameter R is determined based on the target frequency domain cell, or the magnitude of the interleaving parameter R is determined based on the target frequency domain cell group, or the magnitude of the interleaving parameter R is determined based on CORESET; The interleaving parameter C is determined based on the target frequency domain cell, or the interleaving parameter C is determined based on the target frequency domain cell group, or the interleaving parameter C is determined based on CORESET; Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units; The resource unit is one of the following: REG, resource element RE, physical resource block PRB, physical resource group PRG.

35. The apparatus according to any one of claims 27 to 34, wherein, The time-domain resources of the target CORESET are determined based on the target frequency-domain units; and / or, The frequency domain resources of the target CORESET are determined based on the target frequency domain cells; and / or, The size of the time-domain resources of the target CORESET is determined based on the target frequency-domain units; and / or, The size of the frequency domain resources of the target CORESET is determined based on the target frequency domain cells; and / or, The frequency domain resources of the target CORESET are determined based on the priority of the target frequency domain cells; and / or, The frequency domain resources of the target CORESET are determined based on the cascading order of the target frequency domain cells; And / or, The size of the CORESET portion in the target CORESET is determined based on the target frequency domain units; and / or, The size of the CORESET portion group in the target CORESET is determined based on the target frequency domain unit.

36. The apparatus according to any one of claims 27 to 35, wherein, The frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET and the frequency domain resources of the target frequency unit, determined based on the resource indication information of the CORESET. or, The resources of the target CORESET are the intersection of the resources of the CORESET and the resources of the target frequency domain unit, determined based on the resource indication information of the CORESET. or, The frequency domain resources of the target CORESET are the intersection of the frequency domain resources of the CORESET determined based on the resource indication information of the CORESET and the frequency domain resources of the target frequency domain unit, and the interleaving parameter C corresponding to the frequency domain resources of the target CORESET is an integer. Where C = Nreg / (L*R), or, C = floor(Nreg / (L*R)), or, C = ceil(Nreg / (L*R)), or, C = round(Nreg / (L*R)), where floor(·) represents rounding down, ceil(·) represents rounding up, and round(·) represents rounding to the nearest integer. Nreg is the number of CCEs in the time-frequency domain resources of the target CORESET, or, Nreg is the number of CCEs in a portion of the CORESET, or, Nreg is the number of CCEs in the target frequency domain unit, or, N... reg is the number of CCEs in the target frequency domain unit group, or Nreg is the number of CCEs in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units in the time-frequency domain resources of the target CORESET, or Nreg is the number of resource units in a portion of the CORESET, or Nreg is the number of resource units in the target frequency domain unit, or Nreg is the number of resource units in the target frequency domain unit group, or Nreg is the number of resource units in a portion of the time domain resources of the target CORESET, or Nreg is the number of resource units; The resource unit is one of the following: REG, RE, PRB, PRG.

37. The apparatus according to any one of claims 27 to 36, wherein, The aggregation level of the CORESET includes at least one of the following: 1, 2, 3, 4, 5, 6, 7, 8, 16, 32, 64, 128; And / or, The aggregation level of the CORESET is determined based on the size of the REG set, or the aggregation level of the CORESET is determined based on the number of OFDM symbols occupied by the target CORESET; And / or, The aggregation level of the CORESET is determined based on the CORESET, or the aggregation level of the CORESET is determined based on a portion of the CORESET, or the aggregation level of the CORESET is determined based on a group of CORESET portions, or the aggregation level of the CORESET is determined based on the target frequency domain unit, or the aggregation level of the CORESET is determined based on sub-time domain resources.

38. The apparatus according to any one of claims 27 to 37, wherein, The precoding corresponding to the target CORESET is determined based on the CORESET, or the precoding corresponding to the target CORESET is determined based on a portion of the CORESET, or the precoding corresponding to the target CORESET is determined based on a group of CORESET portions, or the precoding corresponding to the target CORESET is determined based on the target frequency domain unit, or the precoding corresponding to the target CORESET is determined based on the sub-time domain unit.

39. A communication device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method as described in any one of claims 1 to 26.

40. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the wireless communication method as described in any one of claims 1 to 26.