CN120457663A

CN120457663A - Controlling the configuration of resource sets

Info

Publication number: CN120457663A
Application number: CN202280102893.3A
Authority: CN
Inventors: 高捷; N·哈特西拉玛尼; R·拉塔苏克; N·芒加尔维德赫
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2022-12-30
Filing date: 2022-12-30
Publication date: 2025-08-08
Also published as: WO2024138639A1

Abstract

Embodiments of the present disclosure relate to configuration of a control resource set (CORESET). A terminal device receives at least one configuration parameter for a control resource set (CORESET) from a network device. The terminal device determines a set of physical resource blocks (PRBs) for the CORESET based on the at least one configuration parameter, wherein the duration of the CORESET includes a plurality of symbols, the number of PRBs in a symbol of the CORESET is different from a multiple of 6, and the number of PRBs in the set is a multiple of 6. In this way, the capacity of the CORESET can be effectively increased.

Description

Configuration of control resource sets

Technical Field

Various example embodiments relate to the field of telecommunications, and more particularly, to an apparatus, method, device, and computer-readable storage medium for controlling the configuration of a set of resources (CORESET).

Background

In the field of communications, there is a continuing evolution that is evolving to provide efficient and reliable solutions for utilizing wireless communication networks. Each new generation has its own technical challenges for handling the different situations and procedures required for connecting and servicing devices connected to a wireless network. In order to meet the ever-increasing demand for wireless data traffic since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) systems, also known as New Radios (NRs). The new communication system may support various types of service applications for the terminal device.

Furthermore, 5G targets new emerging use cases in addition to mobile broadband. The goal of 5G is to achieve significant improvements in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G may also scale to effectively connect to large-scale internet of things (IoT) and may provide a new type of mission critical services.

Disclosure of Invention

In general, example embodiments of the present disclosure provide a solution for the configuration of CORESET.

In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory including instructions that, when executed by the at least one processor, cause the terminal device to at least receive at least one configuration parameter for CORESET from a network device and determine a set of Physical Resource Blocks (PRBs) of CORESET based on the at least one configuration parameter, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in the symbols of CORESET is different than a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In a second aspect, a network device is provided. The network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least transmit to the terminal device at least one configuration parameter for determining a group of PRBs of CORESET, wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in the symbol of CORESET is different from a multiple of 6, and the number of the group of PRBs is a multiple of 6.

In a third aspect, a method is provided. The method includes receiving at least one configuration parameter for CORESET from a network device and determining CORESET a set of PRBs based on the at least one configuration parameter, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in the symbols of CORESET is different than a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In a fourth aspect, a method is provided. The method comprises transmitting to the terminal device at least one configuration parameter for determining CORESET a set of PRBs, wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in the symbols of CORESET is different from a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In a fifth aspect, an apparatus is provided. The apparatus includes means for receiving at least one configuration parameter for CORESET from a network device, and means for determining CORESET a set of PRBs based on the at least one configuration parameter, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in a symbol of CORESET is different than a multiple of 6, and the number of PRBs of the set is a multiple of 6.

In a sixth aspect, an apparatus is provided. The apparatus comprises means for transmitting to a terminal device at least one configuration parameter for determining CORESET a set of PRBs, wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in a symbol of CORESET is different from a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In a seventh aspect, an apparatus is provided. The apparatus includes a receiving circuit configured to receive at least one configuration parameter for CORESET from a network device, and a determining circuit configured to determine a set of Physical Resource Blocks (PRBs) of CORESET based on the at least one configuration parameter, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in a symbol of CORESET is different than a multiple of 6, and the number of PRBs of the set is a multiple of 6.

In an eighth aspect, an apparatus is provided. The apparatus comprises a transmission circuit configured to transmit to a terminal device at least one configuration parameter for determining CORESET a set of PRBs, wherein a duration of CORESET comprises a plurality of symbols, a number of PRBs in a symbol of CORESET being different from a multiple of 6, the number of set of PRBs being a multiple of 6.

In a ninth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the third and fourth aspects above.

In a tenth aspect, there is provided a computer program product comprising program instructions for causing an apparatus to perform at least the method according to any one of the third and fourth aspects above.

It should be understood that the summary is not intended to identify key or essential features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Some example embodiments will now be described with reference to the accompanying drawings, in which:

FIG. 1 illustrates an example communication network in which embodiments of the present disclosure may be implemented;

FIG. 2 illustrates a flow chart of a process for configuring CORESET according to some embodiments of the present disclosure;

FIG. 3 illustrates an example of CORESET configuration in accordance with some embodiments of the present disclosure;

fig. 4A illustrates configuration parameters for CORESET according to 3GPP specifications related to some embodiments of the present disclosure;

Fig. 4B illustrates an example CORESET configuration in accordance with some embodiments of the present disclosure;

Fig. 4C illustrates another example CORESET configuration in accordance with some embodiments of the present disclosure;

fig. 5 illustrates a flowchart of a method for decoding a Physical Downlink Control Channel (PDCCH) according to some embodiments of the present disclosure;

FIG. 6 illustrates an example CORESET mapping according to some embodiments of the disclosure;

Fig. 7 illustrates an example lookup table for CORESET for a Type0-PDCCH according to some embodiments of the present disclosure;

Fig. 8 illustrates an example of CORESET configuration with 16 Resource Blocks (RBs) and 3 symbols, according to some embodiments of the present disclosure;

Fig. 9 illustrates another example of CORESET configuration with 15 RBs and 3 symbols in accordance with some embodiments of the present disclosure;

Fig. 10 illustrates yet another example of CORESET configuration with 15 RBs and 2 symbols in accordance with some embodiments of the present disclosure;

fig. 11 illustrates an example of CORESET configuration with symbol-level hopping in accordance with some embodiments of the present disclosure;

fig. 12 illustrates an example of CORESET configuration with slot level hopping in accordance with some embodiments of the present disclosure;

fig. 13 illustrates an example of a Resource Element Group (REG) mapping order according to some embodiments of the present disclosure;

fig. 14 illustrates a flow chart of a method implemented at a terminal device according to some embodiments of the present disclosure;

fig. 15 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure;

FIG. 16 shows a simplified block diagram of an apparatus suitable for practicing embodiments of the disclosure, and

Fig. 17 illustrates a block diagram of an example computer-readable medium, according to some embodiments of the disclosure.

Throughout the drawings, the same or like reference numerals refer to the same or like elements.

Detailed Description

Principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes and to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein may be implemented in various ways other than those described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

References in the present disclosure to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It will be understood that, although the terms "first" and "second," etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "has," "having," "contains," and/or "including" when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof. As used herein, "at least one of" < list of two or more elements > ", and" < at least one of list of two or more elements > ", and the like, wherein the two or more elements of the list are connected by" and "or" means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

As used in this disclosure, the term "circuitry" may refer to one or more or all of the following:

(a) Hardware-only circuit implementations (such as implementations in analog and/or digital circuitry only), and

(B) A combination of hardware circuitry and software, for example (if applicable):

(i) A combination of analog and/or digital hardware circuit(s) and software/firmware, and

(Ii) Any portion of the hardware processor(s) (including digital signal processor (s)), software, and memory(s) having software that work together to cause a device such as a mobile phone or server to perform various functions, and

(C) Hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware) for operation, software may not be present when not required for operation.

This definition of "circuitry" applies to all uses of that term in this disclosure (including any claims). As another example, as used in this disclosure, the term "circuitry" also covers an implementation of only hardware circuitry, or a processor (or multiple processors), or a portion of a hardware circuit or processor, and its (or their) accompanying software and/or firmware. For example, where applicable to particular claim elements, the term "circuitry" also covers baseband integrated circuits or processor integrated circuits for a mobile device or similar integrated circuits in a server, a cellular network device, or other computing or network device.

As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), high Speed Packet Access (HSPA), narrowband internet of things (NB-IoT), and the like. Furthermore, the communication between the terminal device and the network device in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and/or any other protocol currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. In view of the rapid development of communications, there will of course also be future types of communication technologies and systems in which the present disclosure may be implemented. The scope of the present disclosure should not be considered limited to the foregoing system only.

As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. A network device may refer to a Base Station (BS) or an Access Point (AP), e.g., a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, a low power node (such as femto, pico), etc., depending on the terminology and technology applied.

The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user Equipment (UE), subscriber Station (SS), portable subscriber station, mobile Station (MS), or Access Terminal (AT). The terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal Digital Assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless Customer Premises Equipment (CPE), internet of things (IoT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronic devices, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

The present disclosure is initially directed to release 18RedCap. However, version 18RedCap UE may not present a problem due to the RAN1 protocol. It can still be applied to another work item for a dedicated spectrum of less than 5MHz for frequency range 1 (FR 1). It may also be applied to passive IoT work items in version 19.

The operating plan (R1-1112398) provides NR support for the dedicated spectrum of less than 5MHz for FR 1. The enhancement of operating NR on dedicated spectrum less than 5MHz is as follows.

In LS to RAN4, in addition to reusing the 5MHz channel bandwidth, RAN1 also assumes that only the 3MHz channel bandwidth is supported and wants to obtain RAN4 response over the maximum transmission bandwidth (number of physical resource blocks) of that channel Bandwidth (BW).

Before obtaining the RAN4 response, RAN1 assumes a maximum transmission bandwidth, 15 or 16 Resource Blocks (RBs) for the 3MHz channel BW for evaluation and analysis. Note that the protocol is included in the LS.

For CORESET #0 configuration of transmission bandwidths less than 5MHz for 3MHz and 5MHz channel bandwidths, the following options were studied:

Option 1 the existing configuration table for 15kHz SCS, 5MHz minimum channel BW (i.e., table 13-1 in TS 38.213) is reused for configuration, and

Option 2 a new CORESET #0 configuration table is to be introduced for the configuration.

Whether and how to recover CORESET #0 PDCCH detection performance was investigated for transmission bandwidths less than 5MHz for 3MHz and 5MHz channel bandwidths. Consider the following options:

Option 1, power boost;

option 2 non-interleaved CCE to REG mapping;

option 3, a new interleaver that ensures that PDCCH is fully mapped in spectrum;

option 4, new aggregation level(s) for fitting spectrum;

The options are PDCCH rate matching;

Option 6. No enhancements are specified.

The control resource set (CORESET) is a set of Physical Resource Blocks (PRBs) in the frequency and time domains that are used to carry a Physical Downlink Control Channel (PDCCH) or Downlink Control Indicator (DCI). The CORESET area is located to a specific area on the New Radio (NR) downlink resource grid.

Based on current 3GPP specifications CORESET may be configured with up to 3 symbols and must span a number of Resource Blocks (RBs) that is a multiple of 6 RBs in the frequency domain. This ensures that the number of Resource Element Groups (REGs) in CORESET is always a multiple of 6. REGs are defined as a set of resources within one PRB and one OFDM symbol. Each REG is mapped to a Control Channel Element (CCE) through non-interleaving or interleaving mapping. The configuration of coreset is provided by frequencyDomainResources (frequency domain resources) per 38.331. This is a 45-bit field, where each bit corresponds to a group of 6 PRBs starting from the first RB group in the bandwidth part (BWP). If the bit value is set to 1, it indicates that the RB group belongs to the CORESET frequency domain resource, and a bit corresponding to a group of RBs that is not completely included in the CORESET configured BWP is set to 0.

However, for terminal devices having a bandwidth portion (BWP) less than 5MHz, when the subcarrier spacing (SCS) is configured to 15kHz, the BWP will be limited to only 15 RBs or 16 RBs. In case each bit in frequencyDomainResources corresponds to 6 PRBs hard coded in the frequency domain, up to 12 PRBs per symbol may be configured to belong to CORESET. The maximum number of CCEs for the downlink PDCCH is limited to only 6 CCEs within 3 symbols. The current standard CCE aggregation levels are 1,2, 4, 8, 16, so the maximum CCE that can be scheduled for a single UE is only 4 CCEs, which is typically insufficient for UEs at the cell edge. Furthermore, if no change is performed to allow for greater PDCCH capacity, the UE will experience serious performance problems, such as ongoing re-establishment procedures when an aggregation level higher than 4 is required.

According to an embodiment of the present disclosure, a scheme for configuring CORESET is provided. According to some embodiments of the present disclosure, the condition that CORESET is limited to a multiple of 6 PRBs per symbol is cancelled, while the total CORESET size maintains the multiple of 6 PRBs. This allows more efficient use of intra-symbol PRBs for PDCCH search space capacity. Furthermore, the hopping scheme provides some additional diversity gain, where each symbol may have a starting position or offset relative to the BWP. The new CORESET mapping and hopping can help solve the problem of insufficient CORESET resource capacity of the terminal device in the case of less than 5MHz and a maximum BWP of 15 PRBs or 16 PRBs, while improving downlink coverage performance, reducing inter-cell interference collision, etc.

The principles and embodiments of the present disclosure will be described in detail below with reference to the drawings. Referring initially to fig. 1, an example communication system 100 is illustrated in which embodiments of the present disclosure may be implemented.

In the description of the example embodiments of the present disclosure, the network environment 100 may also be referred to as a communication system 100 (e.g., a portion of a communication network). For illustrative purposes only, various aspects of the example embodiments will be described in the context of one or more terminal devices and network devices communicating with each other. However, it should be understood that the description herein may be applicable to other types of devices referred to using other terms, or other similar devices.

The network device 110 may provide services to the terminal device 120, and the network device 110 and the terminal device 120 may transmit data and control information to each other. In some embodiments, network device 110 and terminal device 120 may communicate over a direct link/channel.

In the communication system 100, a link from the network device 110 to the terminal device 120 is referred to as a Downlink (DL), and a link from the terminal device 120 to the network device 110 is referred to as an Uplink (UL). In the downlink, network device 110 is a Transmitting (TX) device (or transmitter) and terminal device 120 is a Receiving (RX) device (or receiver). In the uplink, terminal device 120 is a Transmit (TX) device (or transmitter) and network device 110 is an RX device (or receiver). It should be appreciated that network device 110 may provide one or more serving cells. As shown in fig. 1, network device 110 provides one serving cell 102 and terminal device 120 resides on serving cell 102. In some embodiments, network device 110 may provide multiple serving cells. It should be understood that the number of serving cells shown in fig. 1 is for illustration purposes and does not imply any limitation.

Communication in network environment 100 may be implemented in accordance with any suitable communication protocol including, but not limited to, fourth generation (4G) and fifth generation (5G) cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and/or any other protocol currently known or to be developed in the future. In addition, the communication may utilize any suitable wireless communication technology including, but not limited to, code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), time Division Multiple Access (TDMA), frequency Division Duplex (FDD), time Division Duplex (TDD), multiple Input Multiple Output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and/or any other technology currently known or to be developed in the future.

It should be understood that the number of devices shown in fig. 1 and their connection relationships and types are for illustration purposes and are not meant to be limiting. Communication system 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure.

Referring now to fig. 2, a flow chart illustrating a process for configuring CORESET according to some embodiments of the present disclosure is shown. For discussion purposes, process 200 will be described with reference to FIG. 1. Process 200 may involve network device 110 and terminal device 120 as shown in fig. 1. It should be appreciated that although the process 200 for configuring CORESET is described in the communication system 100 of fig. 1, the process is equally applicable to other communication scenarios in which different network devices are jointly deployed to provide respective serving cells.

In process 200, network device 110 transmits (202) at least one configuration parameter 204 for CORESET to terminal device 220. Accordingly, the terminal device 120 receives at least one configuration parameter (204). The terminal device 120 then determines (208) a set of PRBs of CORESET based on the at least one configuration parameter. It can be appreciated that the network device 110 can determine CORESET PRBs according to pre-configured rules, generate and transmit corresponding configuration parameters so that the terminal device can acquire PDCCH based on the configuration parameters of CORESET. CORESET, as determined by network device 110, may be the same as CORESET, as determined by terminal device 120.

Based on the configuration parameters, the terminal device 120 determines CORESET that the duration includes a plurality of symbols, e.g., 2 or 3 symbols. The terminal device 120 also determines CORESET the number of PRBs in the symbol. The number of PRBs per symbol is different from a multiple of 6 and in some embodiments it may be a multiple of 2 or 3. The number of PRBs in the group CORESET is a multiple of 6. Since one CCE consists of 6 REGs and each REG is defined within one PRB, the total size of CORESET is a multiple of 6 PRBs.

In some embodiments, for CORESET with 2 symbols, the number of PRBs in a symbol may be a multiple of 3, such that the total number of PRBs of CORESET is a multiple of 6. In some embodiments, for CORESET with 3 symbols, the number of PRBs in a symbol may be a multiple of 2 and the total number of PRBs is also a multiple of 6.

Fig. 3 illustrates an example of CORESET configuration in accordance with some embodiments of the present disclosure. As shown, the bandwidth portion of the terminal device has a maximum of 11 PRBs and CORESET is configured within 3 symbols. It can be observed that the frequency domain resource for each symbol is 8 PRBs and that the duration of CORESET is 3 symbols, resulting in a total CORESET size of 24 RBs or 4 CCEs. In addition, a hopping aspect is depicted in fig. 3, where each symbol CORESET can have a different starting position (rb-Offset). The hopping scheme will be described in more detail with reference to fig. 11 to 13.

Accordingly, network device 110 may configure terminal device 120 with a BWP having a frequency domain CORESET size that is not a multiple of 6 PRBs on a symbol basis such that the total CORESET size across the configured number of CORESET symbols (i.e., considering both frequency domain and time domain sizes) is a multiple of 6 REGs. Embodiments of the present disclosure may improve the capacity of terminal device 120 in a limited bandwidth CORESET compared to the conventional approach requiring CORESET to have a multiple of 6 PRBs per symbol.

For example, PDCCH capacity for UEs smaller than 5MHz is increased. In BWP with scs=15 kHz less than 5MHz, CORESET would be limited to 36 PRBs or 6 CCEs without the present solution and considering terminal devices with basic PDCCH capability. Note that for example, 8 CCEs are required for the Common Search Space (CSS), and in the case of 6 CCEs, the maximum aggregation level that can be used is 4 CCEs. With the provided solution, PDCCH capacity can be increased to 48 PRBs (8 CCEs), which is a 25% increase. In addition to the increased capacity, note that this approach will allow for scheduling CSS of 8 CCEs from this CORESET.

CORESET symbols may have different rb-Offset relative to the starting resource block of BWP, which would enable the possibility of diversity gain from hopping of the symbols making up CORESET. One method of defining the offset per symbol may be based on the cell PCI having a specific offset per symbol.

The proposed solution may achieve the following further advantages. For example, from the terminal's point of view, the basic decoding of the PDCCH is not changed, and the interleaving and mapping of CCEs to 6 REGs is still maintained. An increase in PDCCH capacity does not result in a loss in performance. The proposed solution may enable configuration CORESET0 for less than 5MHz UEs within less than 5MHz BWP with 15kHz SCS and may improve terminal performance because constant re-establishment is avoided when higher aggregation levels are required. The proposed solution is applicable to other scenarios than less than 5MHz or eRedCap.

To ensure the overall CORESET size requirement, the supported combination of CORESET size in PRBs and CORESET duration in number of symbols can be predefined according to the configuration parameters of CORESET.

Fig. 4A illustrates configuration parameters for CORESET according to 3GPP specifications related to some embodiments of the present disclosure. In fig. 4A, CORESET configuration includes ControlRsourceSet (control resource set) Information Element (IE). ControlRsourceSet may be transmitted from the network device 110 to the terminal device 120 in a Radio Resource Control (RRC) message. ControlRsourceSet IE include higher layer parameters frequencyDomainResources (frequency domain resources), which are bit strings or bitmaps. Each bit of the string corresponds to a group of 6 consecutive PRBs, with the packet starting from the first RB group in BWP (see TS38.213[13], clause 10.1). The first (leftmost/most significant) bit corresponds to the first PRB group in BWP, and so on. A bit set to 1 indicates that the PRB group belongs to the CORESET frequency domain resources. Bits corresponding to a set of PRBs that are not fully contained in the portion of bandwidth CORESET configured within are set to zero (see TS 38.211[16], clause 7.3.2).

Fig. 4B illustrates an example CORESET configuration in accordance with some embodiments of the present disclosure. New CORESET configuration parameters frequencyDomainResourcesSize-r18 (shown in bold in fig. 4B) are introduced.

In the absence of frequencyDomainResourcesSize-r18, the terminal device 120 would consider each bit in the frequencyDomainResources bitmap to correspond to 6 consecutive PRBs. In the presence of this parameter, the parameter value indicates the number of consecutive PRBs, each bit in frequencyDomainResources bitmap corresponding to a given value as shown in fig. 4B.

In the above configuration, frequencyDomainResourcesSize-r18 parameters represent the number of PRBs, respectively. The restrictions on the parameter configuration may be defined according to the following rules to ensure that the number of REGs in CORESET is a multiple of 6.

If frequencyDomainResourcesSize-r18 is set to n2, the terminal device expected duration is set to 3 symbols. This corresponds to the 6 REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n3, the terminal device expected duration is set to 2 symbols. This corresponds to the 6 REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n4, the terminal device expected duration is set to 3 symbols. This corresponds to 12 (6×2) REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n8, the terminal device expected duration is set to 3 symbols. This corresponds to 24 (6×4) REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n9, the terminal device expected duration is set to 2 symbols. This corresponds to 18 (6×3) REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n10, the terminal device expected duration is set to 3 symbols. This corresponds to 30 (6×5) REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n14, the terminal device expected duration is set to 3 symbols. This corresponds to 42 (6×7) REGs available in CORESET.

If frequencyDomainResourcesSize-r18 is set to n15, the terminal device expected duration is set to 2 symbols. This corresponds to 30 (6×5) REGs available in CORESET.

The terminal device 120 may determine the number of resource blocks in the set of resource blocks as the value indicated by the parameter frequencyDomainResourcesSize-r18 and determine CORESET the frequency domain resource further based on a bit string, e.g., one or more bits in the bit string frequencyDomainResources that are "1".

Fig. 4C illustrates another example CORESET configuration in accordance with some embodiments of the present disclosure. New CORESET configuration parameters altFrequencyDomainResourcesSize-r18 (shown in bold in fig. 4C) may be introduced. The new parameters may be binary and in alternative embodiments only one bit is required.

In the absence of this binary parameter, the terminal device 120 would consider each bit in the frequencyDomainResources bitmap to correspond to 6 consecutive PRBs. In the presence of this parameter, the terminal device 120 will consider that each bit in the frequencyDomainResources bitmap corresponds to a different number of consecutive PRBs, depending on the configured parameter value and the value of the duration parameter defining the duration of CORESET. The rule for determining the number of consecutive PRBs represented by each bit in frequencyDomainResources bitmap is as follows:

If the duration is set to 1 symbol, then

If altFrequencyDomainResourcesSize-r18 is set to a value of 0, or a value of 1, each bit of frequencyDomainResources represents 6 PRBs,

Otherwise if the duration is set to 2 symbols

If altFrequencyDomainResourcesSize-r18 is set to a value of 0 or a value of 1, each bit of frequencyDomainResources may represent 3 PRBs or (9 PRBs or 15 PRBs.) it is close to or equal to BWP and is a multiple of 3 instead of a multiple of 6.

Otherwise

If altFrequencyDomainResourcesSize-r18 is set to a value of 0 or a value of 1, each bit of frequencyDomainResources may represent 2 PRBs or (4 PRBs or 8 PRBs or 10 PRBs or 14 PRBs or 16 PRBs.) it is close to or equal to BWP and is a multiple of 2 instead of a multiple of 6.

That is, for a duration of 1 symbol, each bit frequencyDomainResources still represents 6 PRBs as normal configuration. For a duration of 2 symbols, each bit may represent a multiple of 3 PRBs, and the terminal device may select a minimum value (3 PRBs) based on a first value (e.g., value 0) or a maximum allowed within BWP based on a second value (e.g., value 1). For a duration of 3 symbols, each bit may represent a multiple of 2 PRBs, and the terminal device may select a minimum value (2 PRBs) based on a first value (e.g., value 0) or a maximum allowed within BWP based on a second value (e.g., value 1).

Fig. 5 illustrates a flowchart of a method for decoding a Physical Downlink Control Channel (PDCCH) according to some embodiments of the present disclosure. The method 500 may be implemented at the terminal device 120 as shown in fig. 1.

At block 510, the terminal device 120 receives CORESET a configuration. In some embodiments, CORESET configuration may be ControlRsourceSet IE included in the RRC message. ControlRsourceSet IE may include configuration parameters, such as one or more of a bit string, a size parameter, and a duration of CORESET.

At block 520, the terminal device 120 determines CORESET PRB whether the mapping is based on 6 PRBs. In some embodiments, when the size parameter does not exist, the terminal device 120 determines CORESET PRB that the mapping is based on 6 PRBs, i.e., 6 resource blocks of frequency domain resources corresponding to CORESET per bit in the bit string. In this case, the method 500 proceeds to block 530, where the terminal device 120 determines the CCE location using CORESET and configuration according to the legacy 3GPP procedure.

When the size parameter is present, the terminal device 120 determines CORESET PRB that the mapping is not based on 6 PRBs, i.e. each bit in the bit string corresponds to a different number of PRBs than 6. The method 500 then proceeds to block 540 where the terminal device determines the number of CORESET PRB per symbol, i.e., the frequency domain resources of CORESET.

In some embodiments, the size parameter indicates a value that is a multiple of 2 or a multiple of 3. The terminal device 120 may determine the size of the resource block group as the value indicated by the size parameter and determine CORESET frequency domain resources based on the bit string (e.g., bit(s) having a value of 1) and the size of the resource block group.

In some embodiments, the size parameter may indicate a binary value. The terminal device 120 may determine the size of the resource block group based on the binary value and the duration of CORESET. For a duration comprising 2 symbols, when the binary value is equal to a first value (e.g., value 0), the terminal device 120 may determine that the size of the resource block group is 3, and when the binary value is equal to a second value (e.g., value 1), the terminal device 120 may determine that the size of the resource block group is a multiple of 3 and equal to or less than the number of resource blocks in the BWP of the terminal device 120. The first value and the second value are interchangeable.

For a duration comprising 3 symbols, when the binary value is equal to a first value (e.g., value 0), the terminal device 120 may determine that the size of the resource block group is 2, and when the binary value is equal to a second value (e.g., value 1), the terminal device 120 may determine that the size of the resource block group is a multiple of 2 and equal to or less than the number of resource blocks in the BWP of the terminal device 120. The first value and the second value are also interchangeable.

Next, at block 550, the terminal device 120 follows a 3GPP procedure for PDCCH decoding based on the mapped CCE locations.

According to an embodiment of the present disclosure, CORESET configuration parameters may include a bitmap or bit string frequencyDomainResources that indicates the frequency domain resources for CORESET. In the absence of frequencyDomainResourcesSize-r18, each bit corresponds to a group of 6 PRBs, with the packet starting from the first RB group in BWP.

CORESET the configuration parameters may also include a size parameter frequencyDomainResourcesSize-r18, which is an enumerated number or binary number. It establishes the granularity of the number of PRBs of frequencyDomainResources. Note that the UE does not expect a configuration that does not satisfy the following case (number of 1 in bitmap frequencyDomainResourcesSize-r18 duration) mod 6 = 0.CORESET configuration parameters may also include a time domain parameter duration. Which indicates the length of the succession of CORESET in number of symbols.

Fig. 6 illustrates an example CORESET mapping according to some embodiments of the disclosure. Example CORESET map is a non-interleaving case. Bitmaps frequencyDomainResources and frequencyDomainResourcesSize-r18 may be provided to terminal device 120.

If frequencyDomainResourcesSize-r18 are present, the terminal device determines that each bit set to 1 means that those frequencyDomainResourcesSize-r18 PRBs are used for each symbol of PDCCH resources. In the case shown in fig. 6, frequencyDomainResources =10, frequencydomain resource size-r18=9, and duration=2. Note that the granularity of frequencyDomainResources is modified according to the size parameter frequencyDomainResourcesSize, where (number of 1 in bitmap frequencyDomainResourcesSize-r18 x duration) mod 6 = 0. Furthermore, the mapping rules are unchanged. In this regard, the terminal device 120 may utilize conventional implementations, for example, CCE n= { reg6n, reg6n+1, REG6n+5.

The mapping scheme of the present disclosure may also be applied to CORESET (also referred to as CORESET or CORESET0 with index 0) configuration for Type0-PDCCH via the following procedure.

Prior to accessing the cell (CORESET a scenario), the terminal device 120 may receive a Master Information Block (MIB) message from the network device 110 that includes CORESET configuration parameters. In some embodiments, the configuration parameters may include or be used to derive an index for determining the duration of CORESET 0. The terminal device 120 may determine CORESET the duration of 0 by querying a lookup table with an index.

Fig. 7 illustrates an example lookup table for CORESET for a Type0-PDCCH according to some embodiments of the present disclosure. An example lookup table may be found in clause 10 of 3gpp TS 38.213 release 17.3.0. Thus, the terminal device 120 may simply use conventional implementations to map CORESET0 of devices having bandwidths less than 5 MHz. It should be appreciated that look-up tables other than the example in fig. 7 are also applicable.

In some embodiments, terminal device 120 may determine the potential frequency domain resources for CORESET0 based on a PRB per symbol of 15 for less than 5mhz CORESET0 if the number of symbols is 2;

Otherwise if the number of symbols is 3, the PRB per symbol for less than 5mhz CORESET0 is 16.

In some embodiments, the starting PRB of CORESET0 may be defined based on, for example, a Physical Cell Indicator (PCI), and each CORESET0 symbol may be assigned a different offset. Furthermore, if the terminal device 120 cannot decode the PDCCH for search space zero, the cell is considered to be barred.

Fig. 8 illustrates an example of CORESET configuration with 16 Resource Blocks (RBs) and 3 symbols, according to some embodiments of the present disclosure. In fig. 8, for example frequencyDomainResourcesSize-r18=n2 or n4 or n8 or n16, and duration=3 symbols, meaning that CORESET includes 16 PRBs in the frequency domain and 3 symbols in the time domain. Total 48 REGs = 8 CCEs. Referring to fig. 8, different block modes define 8 CCEs. The conventional CORESET configuration uses a maximum of 12 PRBs per symbol, with 2 bits set to 1 in the bitmap, resulting in 6 CCEs (12 PRBs per symbol x 3 symbols), the CORESET configuration in fig. 8 has a capacity gain of 2 additional CCEs (25% more) compared to the conventional CORESET configuration.

Fig. 9 illustrates another example of CORESET configuration with 15 RBs and 3 symbols in accordance with some embodiments of the present disclosure. In fig. 9, for example, frequencyDomainResourcesSize-r18=n2 or n14 (e.g., based on binary values), and duration=3 symbols, meaning that CORESET includes 14 PRBs in the frequency domain and 3 symbols in the time domain. Total 42 REGs = 7 CCEs. Referring to fig. 9, different block modes define 7 CCEs. The conventional CORESET configuration uses a maximum of 12 PRBs per symbol, with 2 bits set to 1 in the bitmap, resulting in 6 CCEs (12 PRBs per symbol x 3 symbols), the CORESET configuration in fig. 9 has a capacity gain of 1 additional CCEs (16.7% more) compared to the conventional CORESET configuration.

Fig. 10 illustrates another example of CORESET configuration with 15 RBs and 2 symbols in accordance with some embodiments of the present disclosure. In fig. 10, for example frequencyDomainResourcesSize-r18=n15, and duration=2 symbols, meaning that CORESET includes 15 PRBs in the frequency domain and 2 symbols in the time domain. Total 30 REGs = 5 CCEs. Referring to fig. 10, different block modes define 5 CCEs. The conventional CORESET configuration uses a maximum of 12 PRBs per symbol, with 2 bits set to 1 in the bitmap, resulting in 4 CCEs (12 PRBs per symbol x 2 symbols), the CORESET configuration in fig. 10 has a capacity gain of 1 additional CCEs (25% more) compared to the conventional CORESET configuration.

Because the bandwidth is only 15 or 16 PRBs, the conventional fixed location for CORESET may result in increased interference in the PDCCH region of the cell. In some embodiments, CORESET hopping may further reduce control channel collisions between cells, thereby improving downlink gain. CORESET hops can include symbol level hops and slot level hops.

Fig. 11 illustrates an example of CORESET configuration with symbol-level hopping, according to some embodiments of the present disclosure. As shown, symbol 0 has a starting PRB to 1rb-offset (rb offset) of BWP, symbol 1 has a starting PRB of 2rb-offset, and symbol 2 has a starting PRB of 0 rb-offset.

In some embodiments, rb-offset for each symbol may be provided explicitly for each symbol. In another embodiment, rb-offset for each symbol of CORESET may be defined based on the PCI of the cell, for example:

symbol xrb-offset = cell PCI mod CORSET-duration.

In some embodiments, to enhance the reliability of downlink common information (SIB 1/SI/paging), the PDCCH may have a larger aggregation level and repeat on the slots for which slot level frequency hopping is configured CORESET. PDCCH decoding may be done independently in each slot or it may be done across slot combinations due to encoding the same content. Meanwhile, redundancy retransmission combinations of PDSCH may be implicitly indicated in conjunction with frequency hopping positions while maintaining consistency of DCI contents of PDCCH, which may be combined.

Fig. 12 illustrates an example of CORESET configuration with slot level hopping in accordance with some embodiments of the present disclosure. In fig. 12, two slots each have a corresponding CORESET. CORESET have different rb-offsets across the slots.

CORESET hop start PRB locations may be defined according to rules. The rules may be based on at least one of the PCI of the cell associated with CORESET, the sequence number of the symbol, or the sequence number of the slot CORESET is transmitted. By way of example, and not limitation, a rule may be defined as follows.

Symbol level hopping:

CORESET starting prb= (PCI MOD (15-8) +n# symbol) MOD (15-8), and

Slot level hopping:

CORESET starting prb= (PCI MOD (15-8) +n# slot) MOD (15-8);

Where the number 15 refers to a total of 15 PRBs in the frequency domain and the number 8 refers to frequencyDomainResources-r18=n8. In addition, CORESET hops may be based on scrambling (slot/PCI/RNTI) for different RVs or message types, and may produce hopping gains. The hopping sequence is applied to generate rb-offset and it may also be pseudo-random, where the seed is established via cell PCI, then in each PDCCH monitoring occasion a different offset is applied to each symbol communicated on the hopping pattern. This would allow unused PRBs in CORESET symbols to be used for diversity gain.

In some embodiments, one or more frequency domain hopping parameters may be transmitted from network device 110 to terminal device 120 in an information element. The frequency domain hopping parameter may include a first parameter to define whether hopping is static or dynamic, i.e., whether the first PRB group is changed per monitoring occasion based on a pseudo-random sequence. The frequency domain hopping parameter may also include a second parameter to define how the terminal device should derive a starting PRB per CORESET symbols. This may be a formula where cell PCI and other factors are used to offset the starting PRB. Network device 110 and terminal device 120 may negotiate a hopping formula before CORESET is transmitted.

Fig. 13 illustrates an example of a Resource Element Group (REG) mapping order according to some embodiments of the present disclosure. The hopping re-mapping still follows the time-domain-first-frequency-domain. In FIG. 13, the mapping is in the order of 0-1-2-3-5 REG. Accordingly, the terminal device 120 may index the REGs using conventional implementations. For interleaved CCE-to-REG mapping, legacy implementations are also applicable. For example, the following legacy interleaver formulas (e.g., in 3gpp TS 38.211 version 17.3.0, clause 7.3.2.2) may be reused for the new CORESET mapping. For CCE to REG mapping L, where The interleaver iX is defined by

x=cR+r

r=0,1,...,R-1

c=0,1,...,C-1

Where R.epsilon. {2,3,6}.

Fig. 14 illustrates a flow chart of a method implemented at a terminal device according to some embodiments of the present disclosure. For ease of understanding, the method 1400 will be described with reference to fig. 1 from the perspective of the terminal device 120.

At block 1410, the terminal device 120 receives at least one configuration parameter for a control resource set (CORESET) from a network device. At block 1420, the terminal device 120 determines CORESET a set of Physical Resource Blocks (PRBs) based on at least one configuration parameter, wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in the symbols of CORESET is different from a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In some example embodiments, the plurality of symbols may include 2 symbols, and the number of PRBs in each of the plurality of symbols is a multiple of 3. In some example embodiments, the plurality of symbols may include 3 symbols, and the number of PRBs in each of the plurality of symbols may be a multiple of 2.

In some example embodiments, CORESET may have an index of 0, and the at least one configuration parameter may include an index for determining the number of the plurality of symbols.

In some example embodiments, in determining CORESET a set of PRBs, terminal device 120 may determine CORESET that the number of PRBs in the symbol is 15 based on determining that the number of symbols is 2. Alternatively or additionally, based on determining the number of the plurality of symbols to be 3, the terminal device 120 may determine the number of PRBs in the symbol of CORESET to be 16.

In some example embodiments, the at least one configuration parameter may include a bit string and a size parameter, the bits in the bit string may indicate whether a set of resource blocks in a bandwidth portion (BWP) of the terminal device belong to CORESET frequency domain resources, and the size parameter may be configured to determine a number of resource blocks in the set of resource blocks.

In some example embodiments, in determining CORESET the set of PRBs, terminal device 120 may determine a number of resource blocks in the set of resource blocks based at least on the size parameter. The terminal device 120 may determine CORESET the frequency domain resources based on the bit string and the size parameter.

In some example embodiments, the size parameter may indicate a value that is a multiple of 2 or a multiple of 3. In determining the number of resource blocks, the terminal device 120 may determine the number of resource blocks as a value indicated by the size parameter.

In some example embodiments, the size parameter may indicate a binary value. In determining the number of resource blocks, the terminal device 120 may determine the number of resource blocks based on the binary value and the duration of CORESET.

In some example embodiments, in the case where the duration includes 2 symbols, the terminal device 120 may determine that the number of resource blocks is 3 based on the binary value being equal to the first value. Alternatively or additionally, the terminal device 120 may determine that the number of resource blocks is a multiple of 3 and equal to or less than the number of resource blocks in the BWP of the terminal device based on the binary value being equal to the second value.

In some example embodiments, in the case where the duration includes 3 symbols, the terminal device 120 may determine that the number of resource blocks is 2 based on the binary value being equal to the first value. Alternatively or additionally, the terminal device 120 may determine that the number of resource blocks is a multiple of 2 and equal to or less than the number of resource blocks in the BWP of the terminal device based on the binary value being equal to the second value.

In some example embodiments, in determining CORESET the set of PRBs, the terminal device 120 may determine the starting PRB in the symbol of CORESET based on the Physical Cell Identifier (PCI) of the cell associated with CORESET. Alternatively or additionally, the terminal device 120 may determine CORESET the starting PRB in the symbol based on the sequence number of the symbol. Alternatively or additionally, the terminal device 120 may determine the starting PRB in the symbol of CORESET based on the sequence number of the slot CORESET transmitted.

In some example embodiments, the at least one configuration parameter may further include at least one frequency domain hopping parameter. In determining CORESET the set of PRBs, the terminal device 120 may determine CORESET a starting PRB in the symbol based on the at least one frequency domain hopping parameter.

In some example embodiments, the at least one frequency domain hopping parameter may include a first parameter defining whether hopping of the starting PRBs is static or dynamic. Alternatively or additionally, the at least one frequency domain hopping parameter may comprise a second parameter defining how to determine a starting PRB in the symbol or in the slot of CORESET.

In some example embodiments, the starting PRB in the symbol may be a first starting PRB in a first symbol of CORESET. The first starting PRB may have a first offset from a starting resource block of the BWP of the terminal device. The first offset may be different from the second offset between the second starting PRB in the second symbol of CORESET and the starting resource block of BWP.

In some example embodiments, the starting PRB in the slot CORESET may be the first starting PRB in the first slot that CORESET is transmitted. The first starting PRB may have a first offset from a starting resource block of the BWP of the terminal device. The first offset may be different from a second offset between a second starting PRB and a starting resource block of BWP in a second slot CORESET to which transmission is repeated.

Fig. 15 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure. For ease of understanding, method 1500 will be described with reference to fig. 1 from the perspective of network device 110.

At block 1510, the network device 110 transmits to the terminal device at least one configuration parameter for determining a set of Physical Resource Blocks (PRBs) of a control resource set (CORESET), wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in the symbols of CORESET is different from a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In some example embodiments, the plurality of symbols may include 2 symbols, and the number of PRBs in each of the plurality of symbols may be a multiple of 3. In some example embodiments, the plurality of symbols may include 3 symbols, and the number of PRBs in each of the plurality of symbols may be a multiple of 2.

In some example embodiments, CORESET may have an index of 0, and the at least one configuration parameter may include an index for determining a number of the plurality of symbols.

In some example embodiments, network device 110 may determine that the number of PRBs in the symbol of CORESET is 15 based on determining that the number of the plurality of symbols is 2. Alternatively or additionally, network device 110 may determine CORESET that the number of PRBs in the symbol is 16 based on determining that the number of the plurality of symbols is 3.

In some example embodiments, the at least one configuration parameter may include a bit string and a size parameter. The bits in the bit string may indicate whether a set of resource blocks in a bandwidth part (BWP) of the terminal device belongs to the frequency domain resource of CORESET. The size parameter may be configured to determine a number of resource blocks in a set of resource blocks.

In some example embodiments, the size parameter may indicate the number of resource blocks that are multiples of 2 or multiples of 3.

In some example embodiments, the size parameter may indicate a binary value and the number of resource blocks may be determined based on the binary value and a duration of CORESET.

In some example embodiments, where the duration includes 2 symbols and the binary value is equal to the first value, the number of resource blocks may be 3. In case the duration comprises 2 symbols and the binary value is equal to the second value, the number of resource blocks may be a multiple of 3 and equal to or smaller than the number of resource blocks in the BWP of the terminal device.

In some example embodiments, where the duration includes 3 symbols and the binary value is equal to the first value, the number of resource blocks may be 2. In case the duration comprises 3 symbols and the binary value is equal to the second value, the number of resource blocks may be a multiple of 2 and equal to or smaller than the number of resource blocks in the BWP of the terminal device.

In some example embodiments, network device 110 may determine the starting PRB in the symbol of CORESET based on a Physical Cell Identifier (PCI) of the cell associated with CORESET. Alternatively or additionally, network device 110 may determine CORESET the starting PRB in the symbol based on the sequence number of the symbol. Alternatively or additionally, network device 110 may determine the starting PRB in the symbol of CORESET based on the sequence number of the slot CORESET transmitted.

In some example embodiments, the at least one configuration parameter may further include at least one frequency domain hopping parameter configured to determine a starting PRB in the symbol of CORESET.

In some embodiments, an apparatus (e.g., terminal device 120) capable of performing method 1400 may include means for performing the corresponding steps of method 1400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

In some embodiments, an apparatus includes means for receiving at a terminal device at least one configuration parameter for a control resource set (CORESET) from a network device, and means for determining CORESET a set of Physical Resource Blocks (PRBs) based on the at least one configuration parameter, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in the symbols of CORESET is different than a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In some example embodiments, the means for determining CORESET a set of PRBs may include at least one of means for determining that a number of PRBs in a symbol of CORESET is 15 based on determining that a number of symbols is 2, or means for determining that a number of PRBs in a symbol of CORESET is 16 based on determining that a number of symbols is 3.

In some example embodiments, the means for determining CORESET a set of PRBs may include means for determining a number of resource blocks in a set of resource blocks based at least on a size parameter and means for determining CORESET a frequency domain resource based on a bit string and the size parameter.

In some example embodiments, the size parameter may indicate a value that is a multiple of 2 or a multiple of 3, and the means for determining the number of resource blocks includes means for determining the number of resource blocks as the value indicated by the size parameter.

In some example embodiments, the size parameter may indicate a binary value and the means for determining the number of resource blocks may include means for determining the number of resource blocks based on the binary value and a duration of CORESET.

In some example embodiments, the means for determining the number of resource blocks based on the binary value and the duration CORESET may include means for determining the number of resource blocks to be 3 based on the determined duration including 2 symbols and the binary value being equal to the first value, and means for determining the number of resource blocks to be a multiple of 3 and equal to or less than the number of resource blocks in the BWP of the terminal device based on the determined duration including 2 symbols and the binary value being equal to the second value.

In some example embodiments, the means for determining the number of resource blocks based on the binary value and the duration CORESET may include means for determining the number of resource blocks to be 2 based on the determination duration including 3 symbols and the binary value being equal to the first value, and means for determining the number of resource blocks to be a multiple of 2 and equal to or less than the number of resource blocks in the BWP of the terminal device based on the determination duration including 3 symbols and the binary value being equal to the second value.

In some example embodiments, the means for determining CORESET a set of PRBs may include means for determining CORESET a starting PRB in a symbol based on at least one of a Physical Cell Identifier (PCI) of a cell associated with CORESET, a sequence number of the symbol, or a sequence number of a slot in which CORESET is transmitted.

In some example embodiments, the at least one configuration parameter may further include at least one frequency domain hopping parameter, and the means for determining CORESET the set of PRBs may include means for determining CORESET a starting PRB in the symbol based on the at least one frequency domain hopping parameter.

In some example embodiments, the at least one frequency domain hopping parameter may include at least one of a first parameter defining whether hopping of starting PRBs is static or dynamic, or a second parameter defining how to determine starting PRBs in symbols or slots of CORESET.

In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1400. In some embodiments, the component comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause execution of the apparatus.

In some embodiments, an apparatus (e.g., network device 110) capable of performing method 1500 may include means for performing the corresponding steps of method 1500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

In some embodiments, an apparatus includes means for transmitting, at a network device, at least one configuration parameter for determining a set of Physical Resource Blocks (PRBs) of a control resource set (CORESET) to a terminal device, wherein a duration of CORESET includes a plurality of symbols, a number of PRBs in a symbol of CORESET is different from a multiple of 6, and the number of the set of PRBs is a multiple of 6.

In some example embodiments, the plurality of symbols may include 2 symbols, and the number of PRBs in each of the plurality of symbols is a multiple of 3. In some example embodiments, the plurality of symbols may include 3 symbols, and the number of PRBs in each of the plurality of symbols is a multiple of 2.

In some example embodiments, the apparatus may further include at least one of means for determining that the number of PRBs in the symbol CORESET is 15 based on determining that the number of the plurality of symbols is 2, or means for determining that the number of PRBs in the symbol CORESET is 16 based on determining that the number of the plurality of symbols is 3.

In some example embodiments, the size parameter may indicate a binary value and the number of resource blocks may be determined based on the binary value and the duration of CORESET.

In some example embodiments, the apparatus may further include means for determining a starting PRB in the symbol of CORESET based on at least one of a Physical Cell Identifier (PCI) of a cell associated with CORESET, a sequence number of the symbol, or a sequence number of a slot in which CORESET is transmitted.

In some example embodiments, the at least one frequency domain hopping parameter may include a first parameter defining whether hopping of the starting PRBs is static or dynamic. The at least one frequency domain hopping parameter may include a second parameter that defines how to determine a starting PRB in the symbol or slot of CORESET.

In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1500. In some embodiments, the component comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause execution of the apparatus.

Fig. 16 is a simplified block diagram of a device 1600 suitable for implementing embodiments of the present disclosure. Device 1600 may be provided to implement a communication device, such as network device 110 or terminal device 120 shown in fig. 1. As shown, device 1600 includes one or more processors 1610, one or more memories 1620 coupled to processors 1610, and one or more communication modules 1640 coupled to processors 1610.

The communication module 1640 is used for bi-directional communication. The communication module 1640 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary to communicate with other network elements.

Processor 1610 may be of any type suitable to the local technology network and may include one or more of general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs), and processors based on a multi-core processor architecture, as non-limiting examples. The device 1600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock that is synchronized to the master processor.

The memory 1620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read Only Memory (ROM) 1624, electrically Programmable Read Only Memory (EPROM), flash memory, hard disks, compact Disks (CD), digital Video Disks (DVD), and other magnetic and/or optical storage. Examples of volatile memory include, but are not limited to, random Access Memory (RAM) 1622 and other volatile memory that will not be maintained during a power outage.

Computer program 1630 includes computer-executable instructions that are executed by an associated processor 1610. Program 1630 may be stored in ROM 1624. Processor 1610 may perform any suitable actions and processes by loading program 1630 into RAM 1622.

Embodiments of the present disclosure may be implemented by means of program 1630 so that device 1600 may perform any of the processes of the present disclosure as discussed with reference to fig. 2, 5, 14, and 15. Embodiments of the present disclosure may also be implemented in hardware or by a combination of software and hardware.

In some embodiments, program 1630 may be tangibly embodied in a computer-readable medium, which may be included in device 1600 (such as in memory 1620) or other storage device accessible by device 1600. Device 1600 may load program 1630 from a computer readable medium into RAM 1622 for execution. The computer readable medium may include any type of tangible, non-volatile storage, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 17 shows an example of a computer readable medium 1600 in the form of a CD or DVD. The computer readable medium has a program 1630 stored thereon.

In general, the various embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides for at least one computer program product, the at least one computer program product being tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises computer executable instructions (such as those included in program modules) that are executed in a device on a target real or virtual processor to implement a process or method as described above with reference to fig. 2, 5, 14 and 15. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote memory storage media.

Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations described above. Examples of carriers include signals, computer readable media, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not signal), rather than on the durability of data storage (e.g., RAM versus ROM).

Moreover, although operations are described in a particular order, this should not be construed as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, comprising:

At least one processor, and

At least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least:

receiving at least one configuration parameter for the set of control resources CORESET from the network device, and

Determining the set of physical resource blocks, PRBs, of CORESET based on the at least one configuration parameter;

wherein the duration of CORESET comprises a plurality of symbols, the number of PRBs in the symbols of CORESET is different than a multiple of 6, and the number of the set of PRBs is a multiple of 6.

2. The terminal device of claim 1, wherein at least one of:

the plurality of symbols comprises 2 symbols and the number of PRBs in each of the plurality of symbols is a multiple of 3, or

The plurality of symbols includes 3 symbols, and the number of PRBs in each of the plurality of symbols is a multiple of 2.

3. The terminal device according to claim 1 or 2, wherein:

the CORESET has index 0, and

The at least one configuration parameter includes an index for determining a number of the plurality of symbols.

4. A terminal device according to claim 3, wherein the terminal device is caused to determine the set of PRBs of CORESET by at least one of:

based on determining the number of the plurality of symbols as 2, determining the number of PRBs in the CORESET symbols as 15, or

Based on determining that the number of the plurality of symbols is 3, the number of PRBs in the CORESET symbols is determined to be 16.

5. The terminal device according to claim 1 or 2, wherein:

The at least one configuration parameter includes a bit string and a size parameter;

the bits in the bit string indicating whether a set of resource blocks in the bandwidth part BWP of the terminal device belongs to the CORESET frequency domain resources, and

The size parameter is configured to determine a number of resource blocks in the set of resource blocks.

6. The terminal device of claim 5, wherein the terminal device is caused to determine the set of PRBs of CORESET by:

Determining the number of resource blocks in the set of resource blocks based at least on the size parameter, and

The frequency domain resource of the CORESET is determined based on the bit string and the size parameter.

7. The terminal device of claim 6, wherein the size parameter indicates a value that is a multiple of 2 or a multiple of 3, and the terminal device is caused to determine the number of resource blocks by:

The number of resource blocks is determined as the value indicated by the size parameter.

8. The terminal device of claim 6, wherein the size parameter indicates a binary value, and the terminal device is caused to determine the number of resource blocks by:

the number of resource blocks is determined based on the binary value and the duration of the CORESET.

9. The terminal device of claim 8, wherein the terminal device is caused to determine the number of resource blocks based on the binary value and the duration of CORESET by:

Determining the number of resource blocks to be 3 based on determining that the duration includes 2 symbols and the binary value is equal to a first value, and

Based on determining that the duration comprises 2 symbols and the binary value is equal to a second value, determining that the number of resource blocks is a multiple of 3 and equal to or less than a number of resource blocks in the BWP of the terminal device.

10. The terminal device of claim 8, wherein the terminal device is caused to determine the number of resource blocks based on the binary value and the duration of CORESET by:

determining the number of resource blocks to be 2 based on determining that the duration includes 3 symbols and the binary value is equal to a first value, and

Based on determining that the duration comprises 3 symbols and the binary value is equal to a second value, determining that the number of resource blocks is a multiple of 2 and equal to or less than a number of resource blocks in the BWP of the terminal device.

11. The terminal device of any of claims 1-10, wherein the terminal device is caused to determine the set of PRBs of the CORESET by determining a starting PRB in the symbol of the CORESET based on at least one of:

A physical cell identifier, PCI, of the cell associated with the CORESET;

The sequence number of the symbol, or

The CORESET is the sequence number of the transmitted slot.

12. The terminal device of any of claims 1-10, wherein the at least one configuration parameter further comprises at least one frequency domain hopping parameter, and the terminal device is caused to determine the set of PRBs of CORESET by:

A starting PRB in the CORESET symbols is determined based on the at least one frequency-domain hopping parameter.

13. The terminal device of claim 12, wherein the at least one frequency domain hopping parameter comprises at least one of:

a first parameter defining whether the hopping of the starting PRB is static or dynamic, or

A second parameter defining how to determine the starting PRB in the symbol or slot of the CORESET.

14. The terminal device of any of claims 11 to 13, wherein:

the starting PRB in the symbol is a first starting PRB in a first symbol of the CORESET;

the first starting PRB having a first offset from a starting resource block of BWP of the terminal device, and

The first offset is different from a second offset between a second starting PRB in a second symbol of the CORESET and the starting resource block of the BWP.

15. The terminal device of any of claims 11 to 13, wherein:

the starting PRB in the slot of the CORESET is a first starting PRB in a first slot in which the CORESET is transmitted;

The first offset is different from a second offset between a second starting PRB in a second slot of the CORESET repeated transmissions and the starting resource block of the BWP.

16. A network device, comprising:

At least one processor, and

At least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least:

At least one configuration parameter for determining a set of Physical Resource Blocks (PRBs) of the control resource set CORESET is transmitted to the terminal device,

17. The network device of claim 16, wherein at least one of:

18. The network device of claim 16 or 17, wherein:

the CORESET has index 0, and

19. The network device of claim 18, wherein the network device is further caused to at least one of:

20. The network device of claim 16 or 17, wherein:

21. The network device of claim 20, wherein the size parameter indicates the number of resource blocks that are multiples of 2 or multiples of 3.

22. The network device of claim 20, wherein:

The size parameter indicating a binary value, and

23. The network device of claim 22, wherein:

in case the duration comprises 2 symbols and the binary value is equal to a first value, the number of resource blocks is 3, and

In case the duration comprises 2 symbols and the binary value is equal to a second value, the number of resource blocks is a multiple of 3 and equal to or smaller than the number of resource blocks in the BWP of the terminal device.

24. The network device of claim 22, wherein:

In case the duration comprises 3 symbols and the binary value is equal to a first value, the number of resource blocks is 2, and

In case the duration comprises 3 symbols and the binary value is equal to a second value, the number of resource blocks is a multiple of 2 and equal to or smaller than the number of resource blocks in the BWP of the terminal device.

25. The network device of any of claims 16 to 24, wherein the network device is further caused to determine a starting PRB in the symbol of CORESET based on at least one of:

A physical cell identifier, PCI, of the cell associated with the CORESET;

The sequence number of the symbol, or

The CORESET is the sequence number of the transmitted slot.

26. The network device of any of claims 16 to 24, wherein the at least one configuration parameter further comprises at least one frequency domain hopping parameter configured to determine a starting PRB in the CORESET symbols.

27. The network device of claim 26, wherein the at least one frequency domain hopping parameter comprises at least one of:

28. The network device of any of claims 25 to 27, wherein:

29. The network device of any of claims 25 to 27, wherein:

30. A method, comprising:

receiving at least one configuration parameter for a control resource set CORESET from a network device at a terminal device, and

Determining the set of physical resource blocks PRB of CORESET based on the at least one configuration parameter,

31. A method, comprising:

at least one configuration parameter for determining a set of physical resource blocks PRBs of the control resource set CORESET is transmitted to the terminal device at the network device,

32. An apparatus, comprising:

means for receiving at least one configuration parameter for the set of control resources CORESET from the network device at the terminal device, and

Means for determining the set of physical resource blocks PRB of CORESET based on the at least one configuration parameter,

33. An apparatus, comprising:

means for transmitting at least one configuration parameter for determining a set of physical resource blocks PRBs of the control resource set CORESET to the terminal device at the network device,

34. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 30 or 31.